On 5/26/11 1:25 PM, Ryosuke Niwa wrote:
On Thu, May 26, 2011 at 10:13 AM, Boris Zbarsky <bzbar...@mit.edu <mailto:bzbar...@mit.edu>> wrote:On 5/26/11 12:53 PM, Ryosuke Niwa wrote: And WebKit is also a part of Mac OS X framework and native applications that use WebKit as a part of their applications have no incentive to support Trident, Gecko, or Opera behaviors. I think this particular argument should have next to no weight when deciding on _web_ behaviors. That applies to all of the embeddable rendering engines; interactions between them and non-web embedders should NOT be the web's problem. Sure. I'm just saying that it'll be hard for us to drop the support for other elements in practice. I have no problem with spec not including those elements.
Yes, I understand what you're saying. What I'm saying is that making your web-facing behavior depend on what your non-web consumers want is bad for the web, no matter what the spec says.
-Boris
