- From: Brian Blakely <anewpage.media@gmail.com>
- Date: Thu, 2 Jun 2011 09:27:01 -0400
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: www-style@w3.org
Received on Thursday, 2 June 2011 13:27:48 UTC
Boris, That is why support for inline elements was originally removed. Which is silly. There is a very strong precedent path for cases where popular, but varying, implementations are introduced into spec. Restored support for inline elements should follow an analysis of current implementations, and either a single implementation is chosen as the standard, or an amalgam that optimally satisfies. As with everything, vendors will/won't modify their implementations once the draft is updated, but spec omission shouldn't be an available excuse to leave a good feature on the table. To expedite resolution, I will create some additional, tangible test cases and introduce a proposal for discussion. -Brian On Thu, Jun 2, 2011 at 8:16 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 6/2/11 12:41 AM, Brian Blakely wrote: > >> *Point 1:* >> >> Three major browsers (Firefox, IE, Opera) already behave as desired. >> > > Note that they don't all behave in the same way last I checked; the spec > would need to define behavior here... > > -Boris >
Received on Thursday, 2 June 2011 13:27:48 UTC