https://bugzilla.wikimedia.org/show_bug.cgi?id=27488
--- Comment #31 from Krinkle <[email protected]> 2011-04-11 22:17:54 UTC --- Just so you know, the issue is in BugZilla and it's known to the developers. The following solution are proposed and/or will be implemented, please be patient while they are being executing and pend review and deployment * Implement a way to define a core module as position 'top'. This will fix problems such as with LiquidThreads' styling being loaded too late. LiquidThreads will split it's modules into two definitions: One part that is required for the initial page (probably only css) and a part that runs as soon as the page is ready (everything else) * Add this method as an option to gadgets (scripts and/or style enhancements that need to be loaded before the rest of the HTML is loaded by the browser) * Close this bug. Another note: There is a difference between the "dom-ready" point and the "page is fully rendered" point. Namely, one is $(document).ready the other is $(window).ready. The former is called as soon as the parser reached the bottom of the page and all raw HTML is sent to the browser. The latter is called after the browser is ready interpreting all this and loading images etc. If you need to for example insert a link in a dropdown menu your script should NOT load in the <head> as that dropdown menu will not exist at this point. How was that done in 1.16 ? In the past these kind of scripts had to be called through addOnloadHook, which was called... at the bottom of the page. There is no point in loading a script in the <head> and then calling only a function through addOnloadHook, that causes unnecessary slow pages with no gain at all. -- 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
