Thank you, Karl. That worked great and it retrieved the meta it is trying to retrieve. I have some bits and pieces I need to submit. But here are a couple more questions:

- For the anchor element type, I think it needs a couple of the properties that we make use of on the URL class. Would it be ok to add a couple of these things to case "a" like
case "a":
c = new Anchor();
c.protocol = "";
c.pathname = "";
break;

- xq wants document.createElementNS. Does this ring a bell? Maybe this would just be a wrapper to createElement which supplies the string "http://www.w3.org/1999/xhtml";

Is namespaces a real issue or just a nominal, placeholder issue? It seems to me that it is just a nominal issue because MDN gives four valid namespace URIs, only one of which we would care about. They are for HTML, SVG, XBL and XUL. Who cares about the latter three? We don't support them, so I don't think we would hit name collisions between them.

- I think there is something going on with cloneNode and whether cloneNode clones event handler code. So that's an interesting problem. Why now.. why not before now... I think maybe it's tested for in some versions of a library, like jquery, and maybe it wasn't previously.

thanks
Kevin



On Sun, 10 Dec 2017, Karl Dahlke wrote:

Well it's true that document.head doesn't exist when startwindow runs, but Head 
does, so how bout

Head.prototype.querySelector = function(x) { return querySelectorAll(x)[0] }

Would something like that work?

Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev


--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Reply via email to