Thanks for valuable info!
But these aren't really "attributes", at least in the HTML sense. They're
what I call custom properties, and a central plank of object-oriented
javascript t'boot. I use them all the time, but had no idea they were called
"expandos" (horrid name), or - more importantly -
> Please correct me if I'm understanding this the wrong way. Strings are safe.
> Object references are not.
That's correct. It's safe to store primitives in an expando because
the aren't reference counted for garbage collection. But objects are
trouble. An IE memory leak pattern is as simple as
Expandos are not proprietary to Microsoft. They are custom attributes. For
instance:
var oDiv = document.getElementById('myDiv');
oDiv.collapsible = "true"; // safe expando
var oSpan = document.getElementById('mySpan');
oDiv.relatedSpan = oSpan; // potentially dangerous expando
oDiv.relatedSp
@ <[EMAIL PROTECTED]> :
> Fil, did you ever get a definition of "DOM 0 expandos"...
Now I got plenty, thanks :)
-- Fil
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
I'm confused. Are these expandos proprietory Microsoft attributes with a
specific meaning, or can it also apply to a non-standard attribute that I
may invent for a particular purpose (eg all collapsible elements on a page
might have a custom attribute collapsible="true")? If it's the latter, I
don
I believe so. As I said an "expando" attribute is basically any
non-standard attribute that gets added to an element (doesn't matter
how).
As Klaus notes, the memory leakage is only a problem in IE when the
attribute references other DOM elements (directly, or indirectly via
closures).
Karl Rudd
Karl Rudd schrieb:
> Err no, actually "expandos" refers to "non-standard" attributes that
> get added to DOM elements. They "expand" the attributes that are
> available on an element.
>
> For instance adding an "expando" attribute called "hello":
>
>
>
> Because they're "non-standard" they
so any non standard attribute accessed simple as object.hello is an
expando? no matter if you call getAttribute or not??
On 2/28/07, Karl Rudd <[EMAIL PROTECTED]> wrote:
> Err no, actually "expandos" refers to "non-standard" attributes that
> get added to DOM elements. They "expand" the attribut
Karl Rudd wrote:
> Err no, actually "expandos" refers to "non-standard" attributes that
> get added to DOM elements. They "expand" the attributes that are
> available on an element.
>
> For instance adding an "expando" attribute called "hello":
>
>
>
> Because they're "non-standard" they can c
Err no, actually "expandos" refers to "non-standard" attributes that
get added to DOM elements. They "expand" the attributes that are
available on an element.
For instance adding an "expando" attribute called "hello":
Because they're "non-standard" they can cause memory leak problems
under
Fil, did you ever get a definition of "DOM 0 expandos"...
they're the shortcuts that were provided with dom level 0, that are
short cuts for certain html(only) attributes, and collections of dom
nodes.
like
a.href is an 'expando' whereas a. a.getAttribute('href') is not.
and
document.forms is
We just disabled the test suite - and re-released 1.1.2. We're working
on building a new test suite that doesn't crash Safari. (It's related
to the suite itself, not necessarily the jQuery library.)
--John
On 2/28/07, rolfsf <[EMAIL PROTECTED]> wrote:
>
> Not sure if this is bug-related or not, b
Not sure if this is bug-related or not, but if I try to open the test page in
the full release of 1.1.2 (test/index.htm) it crashes Safari (2.0.4) every
time. FWIW.
John Resig wrote:
>
> As always, if you have any questions or concerns with new release,
> please feel free to discuss it on the
wonderfull!!
good luck with bug hunting/fixing
2007/2/28, John Resig <[EMAIL PROTECTED]>:
Mark -
Yep, we have fixes for those animation bugs, but we're in the process
of testing them more (after which we'll release them).
--John
On 2/28/07, Mark <[EMAIL PROTECTED]> wrote:
> nice to see a bug
Mark -
Yep, we have fixes for those animation bugs, but we're in the process
of testing them more (after which we'll release them).
--John
On 2/28/07, Mark <[EMAIL PROTECTED]> wrote:
> nice to see a bug fix release :)
> though atleast one bug is still in.. that`s the fadein and fadeout of a div
nice to see a bug fix release :)
though atleast one bug is still in.. that`s the fadein and fadeout of a div
in internet explorer.. it moves a little when those actions are done in IE
(6)
2007/2/28, Seb Duggan <[EMAIL PROTECTED]>:
I've noticed a problem in Safari too, this time with the datePic
I've noticed a problem in Safari too, this time with the datePicker
plugin (also written by Kelvin - sorry!).
When clicking the date picker icon, Safari immediately crashes every
time when using the 1.1.2 release.
However, I've tested with every single nightly build, from Feb 18 to
Feb 28,
> * Changed: Events are now internally stored in elem.$events rather
> than elem.events (due to a nasty bug relating to DOM 0 expandos).
I'm translating this blog into French, but I can't figure how to translate
this sentence. "DOM 0 expandos" ?
Anyway this is available at http://www.jquery.info/
John, is it possible for the packed version to have a trailing semi-colon at
the end? I get errors for the script I include after jquery if this isn't in
place.
Cheers and thanks for another great release,
Chris
___
jQuery mailing list
discuss@jquery.c
Just to let you know the latest release seems to have caused an issue
with the jScrollpane plugin whereby it crashes Safari on mac, for now
I would stick with the previous release of jQuery until the plugin has
been updated. I have notified Kelvin of the problem, hope he can fix
it it's a great plu
Amazing. I have a demo tomorrow and the bug I have been trying to fix all day
is "weird flickering menus". Then I hit this page for the 20th time today
and what do you know...
John Resig wrote:
>
>
> The most noticeable issue that was resolved was related to
> animation flickers when doing a s
Awesome work! Looking forward to giving this a spin.
--Erik
On 2/27/07, John Resig <[EMAIL PROTECTED]> wrote:
> Hi Everyone -
>
> The release of jQuery 1.1.2 is upon us! This is a another bug fix
> release. We've fixed a number of outstanding issues. The fixes have
> been tested well, so there s
Hi Everyone -
The release of jQuery 1.1.2 is upon us! This is a another bug fix
release. We've fixed a number of outstanding issues. The fixes have
been tested well, so there shouldn't be any regressions (knock on
wood). The most noticeable issue that was resolved was related to
animation flickers
23 matches
Mail list logo