Andrew,
I wanted to correct this because I feel the history is slightly
different and I didn't like it at that time. Sizzle has never used
DOMSubtreeModified event that I am aware of.
For some time John Resig used something like the DOM Mutation Events
and technique I was already using in
I have this for IE in my event manager:
event.relatedTarget =
event[(event.target == event.fromElement ? 'to' : 'from') +
'Element'];
other browsers would never walk through the above code, they should
not even if just for an initial conditional forking based on browsers.
The
Here is a small quoted text from Andrea Giammarchi on tweetter:
[quote]
i++ returns a new Number with i value then increments the i
reference, while ++i execute just the second step -
that is why I prefer ++i
[/quote]
this should be the same with both pre-increment and pre-decrement
and in my
BenKeen,
you are correct in assuming form fields (elements) contain a form
property, and as said a type property too (also many other elements
has type too).
Keep in mind that it is possible to find/see code using form elements
without nesting them in a real FORM tag (should be bad HTML then,
kangax,
you showed how to correctly use a context in Prototype selectors and
still perform fast (without repeating the context).
Another problem, from what I understand, is that this will only work
if the user doesn't care about the order of elements being returned or
if the order is known
$$() method.
Diego Perini
On 19 Apr, 20:37, BenKeen ben.k...@gmail.com wrote:
Howdy folks,
Quick question: is there a way to extract all elements within a
specific node within a form? What I'm trying to do is get a list of
form fields (select,radio,text input et al) within a particular td
cell
Richard,
On 29 Gen, 17:29, Richard Quadling rquadl...@googlemail.com wrote:
2009/1/29 Diego Perini diego.per...@gmail.com:
Richard,
On 29 Gen, 13:43, Richard Quadling rquadl...@googlemail.com wrote:
2009/1/28 Diego Perini diego.per...@gmail.com:
The other good thing you
Dane,
I completely agree with you about JSLint and lint in general.
For me JSLint is a great debugging tool, it think of it being a real
good, unpaid, advisor.
A tip you may find useful to maintain your nice efforts with less
pain, instead of turning each while loop having an embedded
it is easier
to paste a URL here with the example:
http://pastebin.com/f6264fce4
Thanx for the replies anyways :)
Daniel
2009/1/11 Diego Perini diego.per...@gmail.com:
Should use the this keyword, the specs says that in event handlers
the this keyword is a reference to the element
Daniel,
this is a copy of current Prototype firstDescendant modified to fit.
lastDescendant: function(element) {
element = $(element).lastChild;
while (element element.nodeType != 1) element =
element.previousSibling;
return $(element);
},
Isn't this what you need ?
Diego
On
Should use the this keyword, the specs says that in event handlers
the this keyword is a reference to the element on which the event
was registered.
So the this keyword is equal to the currentTarget event property
when the eventPhase is AT_TARGET (2), if you use observe() in
Prototype I believe
write down of the
features I remember.
Let me know if I can help with extra informations about it.
--
Diego Perini
On 23 Ott, 01:59, Tobie Langel [EMAIL PROTECTED] wrote:
Proper benchmarking (i.e. something more reliable than slickspeed)
would be very useful for making such a decision
Lines:
663:'$=': function(nv, v) { return nv == v || nv
nv.endsWith(v); },
664:'*=': function(nv, v) { return nv == v || nv
nv.include(v); },
665:'$=': function(nv, v) { return nv.endsWith(v); },
666:'*=': function(nv, v) { return nv.include(v); },
are duplicates...found in:
will then behave as appendChild as you said.
These cases should be part of the test unit.
--
Diego Perini
On 24 Set, 07:17, John-David Dalton [EMAIL PROTECTED]
wrote:
@Kangax
I am not aware of any issues with insertBefore and table elements. I
know that IE has issues with innerHTML and table
.
--
Diego Perini
--~--~-~--~~~---~--~~
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 this group, send email to [EMAIL PROTECTED
.
--
Diego Perini
On 12 Giu, 12:46, Nick Stakenburg [EMAIL PROTECTED] wrote:
Diego, on IE custom events can't be cancelled. fireEvent will always
fire an event that
bubbles.http://msdn.microsoft.com/en-us/library/ms536423(VS.85).aspx
That's why I'm for making Element#observe handle mouseenter
JDD,
just a minimal note...more of a remember.
I had a look back to your git sources and
if it is still considered applicable I noticed
that the timer variable is not yet cleared,
and since you seemed to agree...
--
Diego Perini
On 13 Mag, 19:50, John-David Dalton [EMAIL PROTECTED]
wrote
on that.
Actually the fix that was needed was to ensure dom:loaded
fires before the onload event in all browser without throwing
the Operation aborted on IE.
--
Diego Perini
On 14 Mag, 23:19, Diego Perini [EMAIL PROTECTED] wrote:
Too many combinations, probably better split that CSSLoaded.
I
Too many combinations, probably better split that CSSLoaded.
I asked Mark Wubben of sIFR to comment here, he may have
much more experience with this specific graphic lag and may
give more bits about Safari/Opera still needing this or not.
--
Diego Perini
On 14 Mag, 19:57, John-David Dalton
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 bubble
are forced to
trust all browsers are single-thread, we don't need that safeguard,
anyway I completely trust you can make the right choice.
I hope not to let you with more concerns than answers. My tests say
everything is working as it should for the dom:loaded part.
--
Diego Perini
On 13 Mag
that newer Opera versions have fixed that flashy behavior.
I haven't incurred much in that problem myself anyway.
--
Diego Perini
On 13 Mag, 19:50, John-David Dalton [EMAIL PROTECTED]
wrote:
Thanks Diego,
Good catch on the timeout, clearing the timer variable is probably the
right way to go
designed for the IE problem, lately
I converted them to be somehow useful for other browsers too.
--
Diego Perini
On 13 Mag, 23:02, John-David Dalton [EMAIL PROTECTED]
wrote:
Ahh ok,
And Safari also shows this flashy behavior?
--~--~-~--~~~---~--~~
You received
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-gotcha-w
if for example lazy loading
is used. It can probably be used too with big DOM changes.
Thank you for your comments about my trick, hope it can
do for Protoype next version.
Diego Perini
On 12 Mag, 16:02, Nick Stakenburg [EMAIL PROTECTED] wrote:
Thanks John.
My point is that dom:loaded should
me why I am getting back an event of type
dataavailable from an observer registered on DOMContentLoaded.
--
Diego Perini
On 9 Mag, 04:09, Tobie Langel [EMAIL PROTECTED] wrote:
Hi Diego,
Thanks for your feedback.
Actually, yes, the move to git + lighthouse has slowed things down
quite a bit
Because the about:blank URL has no capability of telling
when the main document is complete, it just happen
asynchronously in IE.
On 11 Apr, 02:44, DK [EMAIL PROTECTED] wrote:
Why not use about:blank url?
On Apr 9, 2:12 pm, John-David Dalton [EMAIL PROTECTED]
wrote:
This was originally
It seems that the trick is able to do the job even in IE8b1.
Diego Perini
On 9 Apr, 14:12, John-David Dalton [EMAIL PROTECTED]
wrote:
This was originally used to allow this method to not have to pull down
a real file and to avoid https issues in IE.
This ticket:http://dev.rubyonrails.org
were this is failing. Do you think you can cut out for me the
interesting part of it and post here so I can give it a try ?
Diego Perini
On Feb 25, 7:37 am, Tobie Langel [EMAIL PROTECTED] wrote:
Hi,
I'm all for it myself.
I even had implemented it for 1.6.0.2 and had to revert because
in general.
Diego Perini
--~--~-~--~~~---~--~~
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 this group, send email to [EMAIL
30 matches
Mail list logo
