https://bugzilla.wikimedia.org/show_bug.cgi?id=27488
Nux <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Dynamic CSS not loaded |Move JS libraries back to |immediately |header and do not load the | |dynamically --- Comment #8 from Nux <[email protected]> 2011-03-12 13:50:04 UTC --- The original problem and other similar problems are IMHO all based in one thing - scripts were moved from head to the bottom of a page. This result in scripts being executed at a later phase then before. So yes, as the theory says - the page shows quicker - the problem is you cannot make some scripts. You cannot load any CSS from JS that changes interface without shaking the interface around. AFAIK there is no way to avoid this no. Personally I consider this a regression. Please note that the CSS is not the only problem. Other JS scripts also fire slower. So what happened before? # Head is read. # Scripts and CSS begin to load. # The browser will wait for basic scripts to load before it starts to process the page (by "basic" I mean those that were added with PHP not with JS). # CSS loaded from JS should be ready by now. # Page loads/renders and starts to appear for the user. # In a fraction of a second .ready things are fired and e.g. add links. Correct me if I'm wrong but what happens now is: # Head is read. # CSS begin to load. # Page loads/renders and starts to appear for the user. # Module loader script begin(!) to load. # Modules (only!) begin to load. # Gadgets are being loaded one by one (NOTE! They will wait for each other to load). # Combined site and user script are being loaded (including GeoIP and BannerLoader). # The page is fully displayed and usable by now (by usable I mean user can click on things and use inputs. # Depending on luck (server caching and browser caching) modules and other scripts loaded from JS finish loading and start firing their $.ready. (NOTE! Currently there is a large chance $(alert('here')) called from Gadgets will be called before modules are fully loaded. As modules are in fact libraries this is very bad). # As scripts fire (when loaded, NOT when the page is loaded) page elements move around as other elements are added by scripts. Or am I missing something here? Note that the last part would not be a problem if we wouldn't make any significant changes to the page. The problem is we are. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
