Last modified: 2011-03-13 18:04:43 UTC
The standard parts (the ones that appear on every page) should appear first in the HTML. Currently,
they appear last, so they can't be seen until the rest of the page has loaded, which makes it look
weird and is annoying when you change your mind about viewing that page.
Well, even those "standard" parts are dependent upon the skin...however, the way
it's all added to the markup has to do with the way the CSS for the skins work, etc.
This keeps the page legible in various alternate layouts, screen readers, text-mode browsers, etc.
Thought as much. ;-)
(In reply to comment #2)
> This keeps the page legible in various alternate layouts, screen readers, text-
mode browsers, etc.
Huh (I only reopened the bug because I don't understand)?
MediaWiki can be accessed through more than just a web browser, and not all
browsers use those the same. Google for "screen reader" or "text-mode browser"
I see - with text-mode browsers what appears first in the source always appears
first on-screen? But the header identifies that I am not using a text-mode
browser, so why should I be affected?
(In reply to comment #6)
> I see - with text-mode browsers what appears first in the source always appears
> first on-screen? But the header identifies that I am not using a text-mode
> browser, so why should I be affected?
First of all what header? Second, we serve all user agents the same skin (X)HTML.
It is called a header? I mean the information that is sent by the web browser when
opening a web page. This information includes the name and version of the browser.
Obviously, I meant "Is it called a header?"
I thought a "skin" is the look of a page after it has finished loading, which is
not the issue here - the issue is what order the items appear in the source and
thus how the page appears while it is still loading.