Regarding querySelect, as you see, http://freecarrierlookup.com now runs, so I
don't know if this is still an issue or not.
Well, in freecarrierlookup, it occurred in some pointless google code. I
thought it might be necessary if the google code made the parser bail out
and not run whatever is next, either. But I think this was a mistake.
One slight good thing is that I think probably google ads code is modular
a lot of the time, so if the parser hits a runtime, the ads code did not
have crucial interoperability with the site operation. They *could*
intermingle the two things but in the real world, they usually won't.
Google code is being slotted in like a widget. The freecarrierlookup
developer is not going to intermingle it with their own work unless they
have to.
So we don't need it right now.
As for generally, I don't know. We could wait and see. But I think all
it needs to be is something like,
document.querySelector = function(x) {
return querySelectorAll(x)[0]
}
unless you think the resource hit of selecting all just to throw away the
rest would be not trivial in the case of a
large tree. In that case, unlike getElements, we can't go into the
recursive traversal and say "stop working once you hit the first one,"
because it's third party code. But if we get that far, I am pretty sure
the third party code actually exposes querySelector. I seem to
remember this. The single and multiple are both in MDN:
https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelector
https://developer.mozilla.org/en-US/docs/Web/API/Element/querySelector
https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll
https://developer.mozilla.org/en-US/docs/Web/API/Element/querySelectorAll
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
