Here's a Wikipedia article. There is an error. There is the edit link. Now I click the edit link. It's five seconds after the page has been displayed. Now some Javascript kicks in, that runs 5 seconds after the page first appeared. And it moves the edit link sideways, so instead I click the history link. What!?
Can this stop, please? I have already disabled all personal Javascript and all gadgets.
I run Firefox 3.6.13 on Ubuntu Linux 10.10 on a netbook/laptop with only moderate background load and plenty of RAM. Many users would have less powerful setups.
If Javascript needs to run very late in the page loading process (why?), could it please refrain from rearranging layout elements of the page? It's like a little flea circus doing its tricks for 7-8 seconds after the page loads. I have to sit on my hands, not touching anything until the fleas get tired and stop. All this "usability" and the steward election banner that needs to pop-up before it hides, is soooo very tiring.
I got firebug installed, to study the timing of a loading page. When I reload a page, so all elements are in caches, the first parts including geoip lookup take 60 ms. Then the first images load at +2 seconds. I have no idea what makes it take 2 seconds before the first image is loaded. All images load really fast. Later, after a gap, ext.vector.collapsibleNav, -Tabs, editWarning, and simpleSearch start loading at +4.5 seconds.
Without other running programs, these times shrink to +1 and +2.5 seconds. But there are still inexplicably long gaps between elements. If all images are loaded after 1.4 seconds, why does collapsibleNav start loading at +2.5? This Javascript is going to rearrange the left margin menu, so I'm likely to hit the wrong link when I want to click there.
Happens in Safari too. I was wondering if it was just my set-up, but it seems something is going on. The problem seemed to kick in (for me) sometime yesterday. .
On Thu, Feb 17, 2011 at 2:14 PM, Lars Aronsson lars@aronsson.se wrote:
Here's a Wikipedia article. There is an error. There is the edit link. Now I click the edit link. It's five seconds after the page has been displayed. Now some Javascript kicks in, that runs 5 seconds after the page first appeared. And it moves the edit link sideways, so instead I click the history link. What!?
Can this stop, please? I have already disabled all personal Javascript and all gadgets.
I run Firefox 3.6.13 on Ubuntu Linux 10.10 on a netbook/laptop with only moderate background load and plenty of RAM. Many users would have less powerful setups.
If Javascript needs to run very late in the page loading process (why?), could it please refrain from rearranging layout elements of the page? It's like a little flea circus doing its tricks for 7-8 seconds after the page loads. I have to sit on my hands, not touching anything until the fleas get tired and stop. All this "usability" and the steward election banner that needs to pop-up before it hides, is soooo very tiring.
I got firebug installed, to study the timing of a loading page. When I reload a page, so all elements are in caches, the first parts including geoip lookup take 60 ms. Then the first images load at +2 seconds. I have no idea what makes it take 2 seconds before the first image is loaded. All images load really fast. Later, after a gap, ext.vector.collapsibleNav, -Tabs, editWarning, and simpleSearch start loading at +4.5 seconds.
Without other running programs, these times shrink to +1 and +2.5 seconds. But there are still inexplicably long gaps between elements. If all images are loaded after 1.4 seconds, why does collapsibleNav start loading at +2.5? This Javascript is going to rearrange the left margin menu, so I'm likely to hit the wrong link when I want to click there.
-- Lars Aronsson (lars@aronsson.se) Aronsson Datateknik - http://aronsson.se
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
2011/2/17 Lars Aronsson lars@aronsson.se:
Can this stop, please? I have already disabled all personal Javascript and all gadgets.
There is probably site JS involved. Which wiki is this happening on?
All this "usability" and the steward election banner that needs to pop-up before it hides, is soooo very tiring.
That sounds like a bug in CentralNotice, I've asked Kaldari.
I got firebug installed, to study the timing of a loading page. When I reload a page, so all elements are in caches
No, when you reload, locally cached things are typically ignored. Most pages have a link to themselves (e.g. the "Article" tab), try clicking that instead; that'll probably yield more realistic results.
The general issue you're pointing out is valid, though; ResourceLoader still needs some tweaking and reconsideration.
Roan Kattouw (Catrope)
On 2/17/11 1:57 PM, Roan Kattouw wrote:
All this "usability" and the steward election banner that needs to pop-up before it hides, is soooo very tiring.
That sounds like a bug in CentralNotice, I've asked Kaldari.
It looks like there was an error in the code for that particular banner that was causing it to display a div even when the banner was hidden. Otherwise, you should never see any output from a hidden banner, even for a split second. If this is not the case, please let me know, and let me know which browser it is you're using.
Ryan Kaldari
On 17 February 2011 19:14, Lars Aronsson lars@aronsson.se wrote:
If Javascript needs to run very late in the page loading process (why?), could it please refrain from rearranging layout elements of the page? It's like a little flea circus doing its tricks for 7-8 seconds after the page loads. I have to sit on my hands, not touching anything until the fleas get tired and stop. All this "usability" and the steward election banner that needs to pop-up before it hides, is soooo very tiring.
+1
This was annoying enough during the fundraiser, when the banner would load last thing and steal the click.
- d.
wikitech-l@lists.wikimedia.org