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

2012-01-10 Thread Aryeh Gregor
On Fri, Jan 6, 2012 at 9:47 PM, Ojan Vafai wrote: > 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 > currently is to the new on

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 currently

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 wrote: > What is IE's behavior in this case? IE just ignores as an argument to formatBlock, same as if you pass or something. That matches my current spec, but doesn't match any non-IE browser. Gecko and Presto both try to wrap existing elements

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

2011-05-26 Thread Ehsan Akhgari
On 11-05-26 12:27 PM, Aryeh Gregor wrote: I don't think any of this justifies adding blockquote, which is not supported by all browsers and whose *usual* use is to contain multiple blocks of content. It seems to me that "blockquote" here interferes in functionality with the indent and outdent

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 t

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 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 > blockquote, I'd expect

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 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 what

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 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 thei

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 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 behavior

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 9:27 AM, Aryeh Gregor wrote: > On Thu, May 26, 2011 at 1:56 AM, Ryosuke Niwa wrote: > > WebKit's FormatBlock basically supports all HTML5 elements that are > display: block by default. > > Well, not really. It doesn't support body, ol, or listing, for > instance. It does

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

2011-05-26 Thread Aryeh Gregor
On Thu, May 26, 2011 at 1:56 AM, Ryosuke Niwa wrote: > WebKit's FormatBlock basically supports all HTML5 elements that are display: > block by default. Well, not really. It doesn't support body, ol, or listing, for instance. It does support many more than any other browser does, and I don't th

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

2011-05-25 Thread Ryosuke Niwa
On Mon, May 23, 2011 at 2:37 PM, Aryeh Gregor wrote: > > * Everyone supports address, div, h*, p, pre > * Everyone but IE supports blockquote > * Everyone but Opera supports dd, dt > * Only IE supports ol, ul > * Only Firefox and Chrome support dl > * Only Chrome supports article, aside, footer, he

[whatwg] Request for feedback: supported elements for formatBlock

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