Spent the day thinking hard about about DOM issues/improvements today; group consensus is that MSFT was _TOTALLY RIGHT_ about `element.uniqueID`https://msdn.microsoft.com/en-us/library/ff628794(v=vs.85).aspx …
-
-
Replying to @slightlylate
what's the use case? let's also remember IE used to be the slowest one on the DOM side ...
1 reply 0 retweets 0 likes -
Replying to @WebReflection
Coordination between workers and main-thread DOM
1 reply 0 retweets 1 like -
Replying to @slightlylate
let uid = 0; Object.defineProperty( Node.prototype, 'uniqueID', {get() { return this.nodeType == 9 ? (++uid + Math.random() + '') : Object.defineProperty( this, 'uniqueID', {value: ++uid + Math.random() + ''} ).uniqueID; }} );
2 replies 0 retweets 1 like -
Replying to @WebReflection @slightlylate
I think it numbers based on the DOM structure. (might be thinking of some other IE DOM property, but I remember using it for comparing position of DOM elements)
1 reply 0 retweets 0 likes -
-
Replying to @WebReflection @slightlylate
Looked it up. It was sourceIndex. Used it as replacement for compareDocumentPosition.
1 reply 0 retweets 0 likes -
Replying to @polylem @slightlylate
oh yeah, I remember that one indeed.
@slightlylate is there any proposal for uniqueID in@WHATWG ? will it be ?1 reply 0 retweets 0 likes
Not that I know of, but I think we'll try to revive it. The useful bit will be a getElementById equivalent to go with. MSFT's version overloaded that method, IIRC, which doesn't seem great.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
