Re: [whatwg] Request for feedback: supported elements for formatBlock

2012-01-06 Thread Ojan Vafai
Coming to this discussion very late. Maybe this has already been resolved. FormatBlock should be dumb. It should not try to think about what the author's intended semantics are. It should work on all block elements and should just do the simple changing of the block from whatever type it

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-27 Thread Aryeh Gregor
On Thu, May 26, 2011 at 7:50 PM, Ehsan Akhgari eh...@mozilla.com wrote: What is IE's behavior in this case? IE just ignores blockquote as an argument to formatBlock, same as if you pass quasit or something. That matches my current spec, but doesn't match any non-IE browser. Gecko and Presto

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-26 Thread Boris Zbarsky
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

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-26 Thread Ryosuke Niwa
On Thu, May 26, 2011 at 10:13 AM, Boris Zbarsky 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

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-26 Thread Boris Zbarsky
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

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-26 Thread Ryosuke Niwa
On Thu, May 26, 2011 at 10:40 AM, Boris Zbarsky bzbar...@mit.edu wrote: On 5/26/11 1:25 PM, Ryosuke Niwa wrote: 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

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-26 Thread Aryeh Gregor
On Thu, May 26, 2011 at 12:53 PM, Ryosuke Niwa rn...@webkit.org wrote: The problem is with queryCommandValue.  One of the reasons we support so many block elements is so that queryCommandValue returns a sensible value.  For example, if called queryCommandValue('FormatBlock') inside a

Re: [whatwg] Request for feedback: supported elements for formatBlock

2011-05-26 Thread Ehsan Akhgari
On 11-05-26 4:40 PM, Aryeh Gregor wrote: I'm still skeptical that no web content depends on blockquote being supported by FormatBlock on WebKit. You might argue that they'll have to modify anyway due to IE not supporting it but most of editors do feature / browser detection and heavily rely on

[whatwg] Request for feedback: supported elements for formatBlock

2011-05-23 Thread Aryeh Gregor
execCommand(formatBlock, false, foo) has the effect of replacing the block elements with the given tag. For instance, execCommand(formatBlock, false, p) executed on h1foo/h1 turns it into pfoo/p. However, browsers vary in what elements they accept as arguments, more or less as follows: *