Last modified: 2014-09-23 22:42:30 UTC
go to page https://en.wikisource.org/w/index.php?title=Page:United_States_Statutes_at_Large_Volume_43_Part_2.djvu/153 click edit in the GUI editing toolbar, click Advanced click on Header select box change your mind expected: i should be able to change my mind and not apply header styling actual: i can't get the select box to close. clicking in the text area doesn't dismiss it. even changing to another sub-toolbar doesn't help (it's still open when you go back to advanced).
If you use Chrome developer tools or Firefox's Firebug, does it tell you anything useful about what's going on with the CSS or JS here? Thanks for the report!
While I do have firebug installed, I'm afraid I do not have the magic for figuring out how the CSS or JS might be affecting these elements. (I would be very happy to learn, this is not the first time i've been unable to answer a question like this.) There do not appear to be any scripts attached to any of the dom elements involved, both the CSS and the scripts tabs in firebug are giving me 'access restricted' messages, and the scripts at the bottom of the HTML are mostly URLs rather than in-line scripts.
You have submitted this under ProofreadPage component. Did you try to reproduce this on Wikipedia or other MediaWiki installations?
I'm the one who moved it to the PP component, so if it's not a PP issue please blame me :)
Oh, I did not take a look at history. I don't think it is ProofreadPage extension fault, but let's wait for an input from the reporter to be sure.
This reproduces on a random Wikipedia edit page too. It reproduces in both Chrome and Firefox for the Mac. I'm afraid I'm too new to know what all the various components are, much less which aspects belong to which components. Thanks!
Thanks! No worries, I am updating the report. You should be able to dismiss the dropdown if you click on the header button once again. I am not sure if it is expected behaviour - the dropdown not disappearing after clicking textarea.
I found an earlier report of this problem, so I'm closing this bug as a duplicate. *** This bug has been marked as a duplicate of bug 32731 ***
