<div dir="ltr">On Fri, Jun 13, 2014 at 1:53 AM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@annevk.nl" target="_blank">annevk@annevk.nl</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On Fri, Jun 13, 2014 at 10:32 AM, Ryosuke Niwa <<a href="mailto:rniwa@webkit.org">rniwa@webkit.org</a>> wrote:<br>
> I understand your concern and sentiment but I'm having a hard time imagining<br>
> what kind of problems/concerns would TC39 have with these interfaces that<br>
> are clearly prefixed with DOM.<br>
<br>
</div>That if they end up as objects in JavaScript engines they end up<br>
leaking outside of browsers affecting other parts of the JavaScript<br>
ecosystem. (And actually, we do run new APIs by TC39 for review, so if<br>
these have passed for review on <a href="mailto:public-script-coord@w3.org">public-script-coord@w3.org</a>, perhaps<br>
calling out this implementation tactic, that might be sufficient.)<br></blockquote><div><br></div><div>If that were the concern, we can simply add a private API that WebCore uses to enable these objects at run time.</div>
<div><br></div><div>- R. Niwa</div><div><br></div></div></div></div>