-
-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Collapse-in-comment always starts collapsed #12
Comments
Hi @aspiers! Make sure to reload the page (Shift + F5) after changing the option as the script is loaded into the page and does not refresh because GitHub uses ajax page loading. I just update the documentation to emphasize this necessity. |
|
The setting will always initially show the opposite of the current setting - see line 233. LOL, actually, I just tested it and it does toggle the areas even without a page reload. Maybe there is another script interfering? Are you using Octopatcher? |
Oh, I see! So when I typed in Hmm, this is not an intuitive UI at all. Perhaps you can think of some way to make it clearer, e.g. tweaking the text? |
To be clear, it does work now I understand how it's supposed to work :-) |
What would you suggest? |
In Octopatcher (an addon created from this userscript), I set a select with two options: collapsed & expanded. Does that make more sense? Also, I'm going out of town on the 4th, I'll be unavailable for a month, or so. So please don't think I'm ignoring you if I don't respond. |
That sounds better but I'd have to see it to be sure. |
Updated. |
Thanks - this is better for sure, but the main source of the confusion is still there, i.e. that the value auto-populated in the dialog is the opposite of the current state, so that you only have to click OK to change it. Could the text also give the current state, or clarify this somehow? |
Even if
Start with blocks collapsed?
is set tofalse
, the blocks are still automatically collapsed when an issue loads.The text was updated successfully, but these errors were encountered: