![]() ![]() Of course there are possibilities to scroll, for example via mousewheel. This is especially a problem with long codes like in mediawiki-namespace or userscripts. Long pre's get a scrollbar at the end of the content. The first problem can be fixed with IE-rules, but the second one is something that shouldn't get ignored silently. But it got reverted because of two reasons: This change was discussed on dewiki two years ago and got already implemented in Common.css for a short time. I'd recommend we open another bug for that and (hopefully) fix it in less than 8 years (which is how long this bug survived - having 4 (in) direct duplicates and many on-wiki complaints). I don't think that problem weighs against the aforementioned usability, accessibility and layout issues. For most short sections this isn't an issue, but if the code is taller than the view port then one has to navigate down to find the vertical scroll bar which is quite inconvenient. no laptop touchpad, desktop mouse scrollwheel or mobile touch gesture) then one has to go to the scrollbar in order to scroll. If you're in an environment (device, os and or browser related) where you can't scroll without manually dragging the scrollbar (e.g. Tim Starling brought up an interesting result of this. (there is one on the entire page, but that's afaik very rarely used on the web, and when it is, it is usually a bug).Īll of that is fixed by simply controlling the overflow. When having reached the position in the page where the overflow- is, it is not always obvious to the user how to get to the extra content because there is no scrollbar to see. ![]() This is especially hard to avoid because the layout is fluid, so the position where the text will overlap the image is completely variable and dependent on the font-size and window size / orientation. That made the text completely unreadable, and looks like a broken page (see attached screenshot for a simple example, there are worse examples). Such as image thumbnails, infoboxes, tables, citations and what not. The lack of overflow control is also causing text to run *over* over floated elements.having to scroll back and forth to understand something is very unfriendly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |