W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: Behavior Attachment Redux, was Re: HTML element content models vs. components

From: Dominic Cooney <dominicc@google.com>
Date: Fri, 30 Sep 2011 10:38:59 +0900
Message-ID: <CAHnmYQ8BKMUarEuhazgUXD_n4G2Nojv5Cc8qp9jpvCWBDCBtiQ@mail.gmail.com>
To: "Edward O'Connor" <eoconnor@apple.com>
Cc: public-webapps@w3.org
So, to make this really explicit:

div’s default display is block, but x-div’s default display is inline.

Is there anything else that I missed?

Looking at use cases
<http://wiki.whatwg.org/wiki/Component_Model_Use_Cases>, most of them
would like to be block, or at maybe inline-block.

One philosophical question: Are we optimizing for UAs that support
HTML5, but not the Component Model, handling pages that use the
component model? Or UAs that support HTML4 handling pages that use the
component model? I guess we are _not_ optimizing for old content,
which could in theory use tags that start with x- but not set CSS
display.

Dominic

On Fri, Sep 30, 2011 at 6:45 AM, Edward O'Connor <eoconnor@apple.com> wrote:
>>> If you're talking about bz's second e-mail, then consider cases such as:
>>>
>>>   <p>Foo
>>>   <div> Bar </div>
>>>
>>> ...vs:
>>>
>>>   <p>Foo
>>>   <x-div> Bar </x-div>
>>
>> Can you be a bit more specific and explain the problem you're trying
>> to highlight with this example?
>
> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1162
>
>
> Ted
>
>
Received on Friday, 30 September 2011 01:39:34 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT