Last modified: 2014-04-09 18:20:46 UTC
[[Jyllands-Posten Muhammad cartoons controversy]].
*** Bug 52602 has been marked as a duplicate of this bug. ***
Comments from bug 52602 "Edit notices should scroll when they are larger than the height of the window. Presently the bottom of the message is unreadable. The screenshot attached shows en.wp's "Today's featured article" edit notice displayed in a 581px high window (which is what I normally use for browsing)." The screenshot is attachment 13067 [details] "A couple of users have reported this also happening with "the notice specifically for VE", which I presume is the beta welcome dialog. They are unable to scroll through and read it all."
In general, long edit notices misunderstand the concept of a brief message for users - but yes, we should fix this.
It's not just single long edit notices, combinations of messages can also exceed screen height, e.g. at [[Caucasian Albania]]. The ArbCom sanctions notice is only about 5 lines in the source view, which has vastly greater horizontal space, likewise the semi-protection notice is designed for a horizontal layout. Is there a reason why the VE notices must be vertical? Could they not horizontally expand to fit the messages? Doing so would reduce (but not remove) the need for bug 52471
In terms of combinations, I think we need to plan to support the display of at least three edit notices. It is not at all unusual for articles at the English Wikipedia to display both the standard BLP notice (https://en.wikipedia.org/wiki/Template:BLP_editintro) and a semi-protection notice, and being able to view three means that only one more item could be included. https://en.wikipedia.org/w/index.php?title=Barack_Obama&action=edit&editintro=Template:BLP_editintro shows three items. Some of them have much longer notices. https://en.wikipedia.org/w/index.php?title=Cat&action=edit shows only two, but one has some fairly long collapsed text (which VisualEditor does not collapse).
*** Bug 62408 has been marked as a duplicate of this bug. ***
This was fixed last week.