Ken,
On 14 Mag, 00:23, Ken Snyder <[EMAIL PROTECTED]> wrote:
> Diego Perini wrote:
> > ...
>
> > I believe the last comment in the following related thread by
> > "liorean" says something too (having a separate CSSLoaded event):
>
> >http://my.opera.com/nicomen/blog/2007/07/08/domcontentloaded-go
JD,
I currently use Safari but I never noticed those flash.
Seems both Safari and Konqueror use a different render engine
which is not affected by this small graphic annoyance.
Unfortunately I don't have a good test case for this behavior
and I don't have previous versions of Safari to try, newe
Diego Perini wrote:
> ...
>
> I believe the last comment in the following related thread by
> "liorean" says something too (having a separate CSSLoaded event):
>
> http://my.opera.com/nicomen/blog/2007/07/08/domcontentloaded-gotcha-with-external-stylesheets
> ...
+1 for a separate CSSLoaded event.
I was trying to use the Ajax.Responders.register and the onException
was always running!..
This was a big problem for the application. I follow the exception a
bit and saw the error was:
SyntaxError: invalid label
on line 1337, which is:
return eval((this.transport.responseText || '').unf
Ahh ok,
And Safari also shows this flashy behavior?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from thi
JD,
the Opera check should be considered a user feature request
to avoid the annoying flash in some situations. Since it does
not do any harm, I would leave it in to make users happy;
HTML5 specs leave that decision to implementors.
Later on, that part could be removed when it can be confirmed
th
Thanks Diego,
Good catch on the timeout, clearing the timer variable is probably the
right way to go :)
So maybe we I should remove the Opera check considering other browsers
may support the HTML 5 spec as well.
- JDD
--~--~-~--~~~---~--~~
You received this messag
JD,
the Opera adjustment is probably a "miss-correction" by me originated
from this discussion thread:
http://groups.google.com/group/jquery-dev/browse_thread/thread/ad7e754c0a10f88a/
I said "miss-correction" mainly because the only current specification
I know about this is HTML5 which does not
I think Prototype should support something like this, though I am not
sure if your patch is the best way to do it. I will have to look at it
closer.
I flagged the ticket for 1.6.1.
Also Juriy has his version of simulating events ->
http://github.com/kangax/protolicious/tree/master/event.simulate
Hi,
I've posted a bug (
http://prototype.lighthouseapp.com/projects/8886-prototype/tickets/96-patch-event-fire-emits-normal-html-events
) with a patch for making Event.fire work with regular events. As the
description says, I've tested it with IE6, FF2, FF3, O9.26 and S3,
without any problems.
A
Diego,
Is line 394 ok with a specific check for Opera?
http://github.com/jdalton/prototype/tree/master/src/event.js#L394
I heard Opera 9.5b doesn't have that issue (but I think that may be
getting to granular).
My main goal with the browser sniff is to avoid unnecessary iterations
of the dom on b
John-David,
thank you for the short but effective explanation about that bit...
Diego Perini
On 12 Mag, 19:22, John-David Dalton <[EMAIL PROTECTED]>
wrote:
> Diego Perini,
>
> in IE "dom:loaded" is a custom event, custom event use the
> "ondataaviable" event as a vessel to ride the event bubbl
12 matches
Mail list logo
