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 1/17/14 12:34 AM, Gordon P. Hemsley wrote:
I have finally made this change. Please confirm that this is what you
had in mind:
https://github.com/whatwg/mimesniff/commit/d7bafc16ee480a5dea4c27d60dd5272388e022ce
http://mimesniff.spec.whatwg.org/#rules-for-text-or-binary
Yes, thank you.
Hi,
The HTML spec has an Index section, with tables of all existing
elements, attributes, and other things. I find this very helpful.
When considering what Servo should implement, I mistakenly concluded
that li elements do not have a 'type' attribute, based on the Index.
They in fact do, as
On Thu, 23 Jan 2014, Simon Sapin wrote:
To help with discoverability of obsolete features by implementers, I’d
like them to be included in the Index section’s tables.
They're explicitly excluded to help with avoiding their discovery by
authors.
There's a link from any interface that has
On 23/01/2014 08:54, Ian Hickson wrote:
On Thu, 23 Jan 2014, Simon Sapin wrote:
To help with discoverability of obsolete features by implementers, I’d
like them to be included in the Index section’s tables.
They're explicitly excluded to help with avoiding their discovery by
authors.
I
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
On 1/22/14 6:07 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/22/14 8:14 PM, Bruno Racineux wrote:
Meanwhile, is there a way in which all vendors can prevent their
pre-loaders from preloading (and loading at all for that matter) any
img
that has either: An html5 hidden attribute
This is
On Thu, Jan 23, 2014 at 6:13 PM, Bruno Racineux br...@hexanet.net wrote:
On 1/22/14 6:07 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/22/14 8:14 PM, Bruno Racineux wrote:
Meanwhile, is there a way in which all vendors can prevent their
pre-loaders from preloading (and loading at all for that
On 1/23/14 9:13 PM, Bruno Racineux wrote:
Then how come it is the case right now for both:
object style=display:none data=image.png
Gecko's preloader never preloads objects. There are various reasons
for this, but the most important one is that in practice it doesn't
matter for actual web
11 matches
Mail list logo
