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
Allow choosing content specific notification methods #5
Comments
Hmm, I like the idea in theory - but it is at minimum one extra click to subscribe. |
I wouldn't want to add a setting for this. It adds complexity and settings are difficult to get rid of later. I asked peoples opinion at work and so far everyone is in favor of this change. I really don't think users use the subscribe feature that often. So a couple of extra clicks wouldn't be a problem. I will make a pull request soon so you can also try out the UI. We can decide about the settings later. And yes, I plan to use XHR. I was just wondering whether there should be a submit button that does the XHR request or if each separate checkbox should trigger its own request. |
Been giving this some thought, if there's no submit button, they'll still need to click somewhere to close the dialog anyway, and you have potentially multiple XHR requests to update the selections. If we use a submit button all selections can be sent as a single XHR request and the submit action can trigger the closing of the dialog. |
Good point about having to close the popup anyway. |
Hm... why not use both? Let's have a link that subscribes using default notification settings - no questions asked. And another menu item (small symbol for dropdown menu) that opens the form with content-specific notification settings. |
That sounds good to me, only downside is entity menu congestion, but site owners have to deal with that anyway. Also that make it easier to force one or the other method if the site owner wants a specific UX |
I think I'll finish the 1.9 update without this feature. |
Revisiting this - I like the idea |
It would be cool to allow users decide what notification methods they want to use for each specific content.
The UI Could look something like this:
Each checkbox could trigger an XHR request. Or there could be a submit bottom at the bottom of the popup.
I wonder if users would like this kind of UI change. Would it just make subscribing more difficult? Opinions?
The text was updated successfully, but these errors were encountered: