<br><br><div class="gmail_quote">On Wed, Jul 7, 2010 at 5:24 PM, Peter Kasting <span dir="ltr"><<a href="mailto:pkasting@google.com">pkasting@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im">On Wed, Jul 7, 2010 at 5:00 PM, Dmitry Titov <span dir="ltr"><<a href="mailto:dimich@chromium.org" target="_blank">dimich@chromium.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I'd lean to the removal, unless there is a port that has work ongoing or planned soon for those implementations.</div>
<div><br></div><div>Does anybody vote for #ifdefs?</div></blockquote><div><br></div></div><div>I vote against removal if only because Chromium has really wanted these badly for a long time and simply hasn't been able to find someone to implement them. Perhaps I could make it worth your while to implement rather than remove the stubs? :)</div>
</div></blockquote><div><br></div><div><i>Even if someone to implement them for chromium, it doesn't seem to fix the overall problem. </i>Dmitry indicated that the presences of these is breaking feature detection in browsers using WebKit (-- which is something being heard from web developers).</div>
<div><br></div><div>A simple solution is to remove them. Later, any port (including chromium) who gets someone to work on them could re-add these methods back properly under ifdef's.</div><div><br></div><div>dave</div>
</div>