Hahaha... On Wed, Jan 27, 2010 at 11:34 AM, Roman Land <[email protected]> wrote:
> "Enjoy or else.." brain thrown an error - threat out of context ;) > > Cheers > -- Roman > > > On Wed, Jan 27, 2010 at 9:13 PM, Eneko Alonso <[email protected]>wrote: > >> Hi guys, >> >> After doing some research and testing we have come up with a way to detect >> when CSS is loaded by the browser using Asset.css. >> Internet Explorer and Opera support the onload event. Webkit browsers do >> too, but Chrome never fires that event, at least not all the time (I got it >> to fire from the console a few times). >> Firefox does not support the onload event at all. Other events like >> onreadystatechange seem to work in IE and Opera. >> >> So the solution is to use events for IE and Opera and polling for Webkit >> and browsers that don't support the event. >> >> We have overriden the implementation of Asset.css. Let me know what you >> think: >> http://gist.github.com/288091 >> >> Enjoy or else.. >> >> >> >> On Thu, Jan 21, 2010 at 9:38 AM, Eneko Alonso <[email protected]>wrote: >> >>> Hi there, >>> >>> The documentation says you can add an onload event to Asset.css, but >>> looking at the code, it really does not add the event. Also, doing some >>> testing, seems like the browser (Firefox 3.6) does not fire a load event >>> attached to a link element. >>> Any experience with this? Is the documentation mistaken? >>> >>> Does anyone know a way to detect when a CSS file is loaded by the >>> browser? >>> >>> Thanks >>> >> >> > > > -- > --- > "Make everything as simple as possible, but not simpler." > > - Albert Einstein > >
