Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'chan' parameter, and pre-populating the form with the channel set #12

Open
harry-wood opened this issue Jun 5, 2018 · 1 comment
Open

Comments

@harry-wood
Copy link

In our cgiirc set-up with multiple channels available in a drop-down (Drop-down on the initial form before entering the chat screen), I'd like to be able to share a URL which pre-populates the 'Channel' value.

To my delight I found there is a parameter which does just that! The chan parameter.

...except it doesn't work. It pre-populates the value in the form, but then when we click through we end up connected to the default channel.

@harry-wood
Copy link
Author

harry-wood commented Jul 25, 2018

The actual instance I'm looking at is OpenStreetMap's . So I'm trying to set "chan" like this: https://irc.openstreetmap.org/?chan=osm-gb [update] irc.openstreetmap.org no longer uses CGI:IRC (partly because of this issue)

I could have a go at fixing this myself. Seems pretty simple but...

Can someone who is familiar with the design of this thing, acknowledge this as an issue / offer any thoughts?

I'm a bit confused about the design. With this param passed, it pre-populates the value in the form, but with the field disabled. Why disable it? What is the usage pattern we're expecting for parameters like this? Which aspects of this should be under control of the end-user on the form, end-user via URL params, or administrator config?

I think the "login form" section here: http://cgiirc.org/docs/custom.php documents this a bit, but those links are all dead, making it pretty unclear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant