<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US><div class=WordSection1><p class=MsoNormal>>Might I suggest tagging events with the browser selector and URL?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I use URL when I want to load more than one URL into a browser (just to confound things).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So URL is probably NOT necessary for X3Dv4. Only selector. X_ITE already supports/requires selector for JS at least<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>An example of where x3dom fails, I think, is when two X3DOM browsers have the same DEF value for a node, and you are accessing the DEF through DOM scripting. Should we leave this up to the DOM script to differentiate browsers, essentially anyone who wants to support dual X3DOM browsers are required to use id’s, which make DEFs unique? Or require selectors from the start (we know better than you)?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Go X3DOM!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>