TIL: <span id="foo">nope</span> foo.innerHTML = "How does this even work??"; No querySelector!
-
-
-
Replying to @humphd
I'd love to hear an explanation. Seems like irresponsible namespace pollution.
1 reply 0 retweets 0 likes -
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11960 … and make sure to read to the end. Also https://bugzilla.mozilla.org/show_bug.cgi?id=622491 … and its duplicates and whatnot.
1 reply 1 retweet 1 like -
Replying to @really_bz @bz_moz and
Yeah, this is one of those things that sounds awesome until you realize it’s kinda not.
2 replies 0 retweets 0 likes -
pretty much wtfbbq
1 reply 0 retweets 1 like -
Yeah - I only just learned about this a couple months ago but have been afraid to even try it because eek.
1 reply 0 retweets 0 likes -
Maybe we could use C-style namespacing to avoid conflicts? <div id="moz_jquery_error_bucket"> (sarcasm)
1 reply 0 retweets 0 likes
You can't get conflicts: the global scope polluter will only show things that don't shadow anything.
-
-
. Yes, but you get inconsistencies that way, with some names available and some not. That’s not good.
1 reply 0 retweets 0 likes -
Oh, sure. I'm just saying that the polluter sucks, but at least doesn't break code that isn't trying to use it.
0 replies 0 retweets 0 likes
End of conversation
New conversation -
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.