Glen -
Glenn has the answer.
So we're going to come up with yet-another-registry rather than use one
that already exists and guarantees (at least as far can be guaranteed)
uniqueness: DNS.
The ramifications of not making HTML5 be XHTML5 will be with us for a very
long time indeed.
Cheers,
-
All -
I'm going to throw my 2 cents in here and say that, whatever ends up happening
with scoping, that the equivalent of the current
querySelector()/querySelectorAll() should be named matchesSelector().
As a longtime Web developer (and trainer of other Web developers) it is
important to me
All -
As a longtime developer of client-side Web applications, I have longed for such
a mechanism that would allow the user to explicitly opt-in to allow
cross-origin access.
This access would be:
* explicit opt-in
* per site
I can imagine a user scenario thusly:
- User loads page from
Arve -
Getting the value of 'src' here using
'document.images[0].getAttribute(src)' should return the relative
path.
The Microsoft guys made a big deal out of the fact that IE8 (in IE8
'strict standards' mode) will now properly return the relative path
when 'getAttribute()' is used,
Folks -
First, my apologies if this topic has been discussed before. If so,
just point me to the relevant part of the spec or discussion and I'll
go away :-). I also apologize if this is the wrong group for this
question. If so, point me to the correct one. I haven't been able to
find
