- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 29 Apr 2014 17:55:13 +0000 (UTC)
- To: WHAT Working Group <whatwg@whatwg.org>
- Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, dbaron@mozilla.com
This discussion focused around the various behaviours that browsers have
around the rendering of <br>.
On Thu, 23 Jan 2014, Boris Zbarsky wrote:
>
> What Gecko does with <br> is basically to treat it like a special box
> type that has special sizing/painting/linebreak behavior. But we do
> still allow that box to be positioned/floated, just like an <img>...
On Tue, 28 Jan 2014, Elliott Sprehn wrote:
>
> Blink treats <br> (conceptually) like a subclass of Text, there's
> nothing to style because it's just a run of text with a forced break.
On Wed, 29 Jan 2014, Tab Atkins Jr. wrote:
>
> We talked this over in the CSSWG meeting, and came up with a proposal
> for non-magical styling that is still very close to current behavior in
> all browsers:
>
> br {
> display-box: contents;
> content: "\A";
> white-space: pre;
> }
I've filed a bug to track this. It would be useful if browser vendors
could indicate whether they think Tab's proposal is satisfactory (in
particular, is 'display-box' something that browsers will implement?
Apparently Gecko is doing it, anyone else?).
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25503
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 29 April 2014 17:56:31 UTC