We shouldn't fragment WebKit engine behavior like that, especially when the feature is already being used to detect WebKit browsers (any WebKit-based browser would just be shooting itself in the foot by removing support for this). My vote would be to just spec it. If Trident and WebKit already do it, let's just spec it and then FF and Opera can implement it too.
dave (hy...@apple.com) On Mar 1, 2012, at 2:07 PM, Erik Arvidsson wrote: > How about making this a compile time flag or runtime flag so that > Apple Dashboard and iOS can keep it but let other users of WebKit > disable it? > > erik > > > > > On Tue, Feb 28, 2012 at 22:23, Benjamin Poulain <benja...@webkit.org> wrote: >> On Tue, Feb 28, 2012 at 9:48 PM, <t...@codeaurora.org> wrote: >>> Seriously, I'm not sure how to proceed on this. It does seem to be >>> outside the spec. >> >> Either update the spec or create a path to deprecate the "bug". >> >> Personally, this "feature" sounds like it could be useful for web >> developers so updating the spec might not be a bad idea. >> >> Benjamin >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
