[ resending this message, originally dated Date: Tue, 29 Apr 2014
11:42:10 -0700, since I just noticed it didn't make it through to
the list due to the list's content-type filters rejecting signed
messages ]
On Tuesday 2014-04-29 17:55 +, Ian Hickson wrote:
On Wed, 29 Jan 2014, Tab
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
On Wed, Jan 22, 2014 at 1:51 PM, Daniel Holbert dholb...@mozilla.com wrote:
Hi folks,
Boris Zbarsky and I ran across a not reflecting reality issue in the
WHATWG HTML spec.
The spec currently defines the rendering of the br element as follows:
# br { content: '\A'; white-space: pre; }
On Thu, Jan 23, 2014 at 10:54 AM, Daniel Holbert dholb...@mozilla.comwrote:
On 01/23/2014 03:16 AM, Stewart Brodie wrote:
[2] I only noticed one rendering difference -- IE11 honors border on
br, unlike the other browsers that I tested. (It still doesn't honor
e.g. display/width/height,
On Tue, Jan 28, 2014 at 1:04 AM, Elliott Sprehn espr...@gmail.com wrote:
On Thu, Jan 23, 2014 at 10:54 AM, Daniel Holbert dholb...@mozilla.comwrote:
On 01/23/2014 03:16 AM, Stewart Brodie wrote:
[2] I only noticed one rendering difference -- IE11 honors border on
br, unlike the other
On 1/28/14 1:04 AM, Elliott Sprehn espr...@gmail.com 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.
I'd just like to note that 'inline' styling for br should be allowed.
I have been using it for a
Daniel Holbert dholb...@mozilla.com wrote:
So: to reflect reality, it might be better to specify br in a way that
doesn't suggest it's as customizable with CSS. (for the white-space
property in particular, but probably others as well)
For reference, here's a page with a few testcases:
On 1/23/14 6:16 AM, Stewart Brodie wrote:
I get different results on your test case for the bottom two tests. In
Chrome 33 and Opera 12.16 (Linux), there is a line break; in Firefox 26
there isn't.
Indeed.
What Gecko does with br is basically to treat it like a special box
type that has
On 01/23/2014 03:16 AM, Stewart Brodie wrote:
[2] I only noticed one rendering difference -- IE11 honors border on
br, unlike the other browsers that I tested. (It still doesn't honor
e.g. display/width/height, though.)
I get different results on your test case for the bottom two tests. In
On 1/23/14 1:54 PM, Daniel Holbert wrote:
So, the position float properties do represent a little bit of
style that Gecko honors on br (but not Blink/Presto; not sure about IE).
IE11 shows linebreaks on your last two testcases there.
-Boris
Note: part of the motivation for this concern is that the CSS Flexbox
spec likely needs a bit of tweaking to indicate how br elements in
runs of raw text should be handled, as I noted in this post to www-style:
http://lists.w3.org/Archives/Public/www-style/2014Jan/0317.html
...and the new spec
On Wed, 22 Jan 2014, Daniel Holbert wrote:
Boris Zbarsky and I ran across a not reflecting reality issue in the
WHATWG HTML spec.
The spec currently defines the rendering of the br element as follows:
# br { content: '\A'; white-space: pre; }
Source:
12 matches
Mail list logo
