On Wed, 15 Jun 2011, Jukka K. Korpela wrote:
2011-06-15 3:26, Ian Hickson wrote:
Styling a whole document by having style sheets in the middle of the
document causes flickering (as the browser updates the styles), and is
hard to maintain. So we make this non-conforming, to help authors
2011-06-15 3:26, Ian Hickson wrote:
Styling a whole document by having style sheets in the middle of the
document causes flickering (as the browser updates the styles),
Good point (though it's really may cause rather than causes.)
and is
hard to maintain. So we make this non-conforming, to
On Fri, Mar 25, 2011 at 3:37 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Are there any other reasons to allow style as flow content?
That is, are there good use cases for it?
MXR uses style in flow to give updated search results on the fly
without requiring JavaScript.
Eduard Pascual wrote:
If you look closer at the scenario you describe (having control over
sparse parts of the body, but not the full document), we don't
really want to enable un-scoped stylesheets there: they could easily
interfere with (up to completely screwing up) the parts of the
document
On Mon, Mar 28, 2011 at 7:23 AM, Jukka K. Korpela jkorp...@cs.tut.fiwrote:
Boris Zbarsky wrote:
If you can only affect _some_ parts of the body you should in fact
be using style scoped, no?
No, because the parts might appear around the body so that you cannot use
any wrapper that
Jukka K. Korpela:
Yet another reason for dropping style scoped in favor of an attribute
referring to an external stylesheet.
I’m not sure which of these I would hate the least:
blockquote stylesheet=external.css…
blockquote style=@import external.css;…
blockquotestyle scoped
Boris Zbarsky wrote:
On 3/25/11 9:49 PM, Nils Dagsson Moskopp wrote:
More precisely, under what circumstances does
an author have control over the very start ofbody, but not over
head?
I can see how some sort of template setups might have that, where the
head is controlled by the overall
On 3/27/11 3:21 AM, Jukka K. Korpela wrote:
It is a rather common setup in websites that offer the public an
opportunity to publish for free. I've been told eBay is an example of
that: you can only affect some parts of the body.
If you can only affect _some_ parts of the body you should in
On Sun, Mar 27, 2011 at 2:30 PM, Boris Zbarsky bzbar...@mit.edu wrote:
The use case for unscoped style outside head is if you have full control
over the body but no control over head.
Then why don't you just make style scoped a child of the body? Is
it somehow essential that you be able to
Boris Zbarsky wrote:
If you can only affect _some_ parts of the body you should in fact
be using style scoped, no?
No, because the parts might appear around the body so that you cannot use
any wrapper that contains them all. It would be awkward to use copies of the
same stylesheet in
On 3/25/11 9:49 PM, Nils Dagsson Moskopp wrote:
More precisely, under what circumstances does
an author have control over the very start ofbody, but not over
head?
I can see how some sort of template setups might have that, where the
head is controlled by the overall site but the body is
Boris Zbarsky wrote:
On 3/24/11 9:29 PM, Nicholas Zakas wrote:
[...]
Fixing the issue results in:
div
style scoped.foo { color: red; }/div
/div
The correct fix for this issue is to put this style in the head,
isn't it? Why would would you fix it by adding @scoped?
There is nothing
The part of the spec that defines what browsers are supposed to do
already reflects current browser behavior.
Can you point me to that?
And if the spec already specifies the current browser behavior, why does the
definition of style require the scoped attribute in flow content? This seems
On 3/25/11 12:53 PM, Nicholas Zakas wrote:
The part of the spec that defines what browsers are supposed to do
already reflects current browser behavior.
Can you point me to that?
http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#attr-style-scoped
second paragraph:
On Thu, Mar 24, 2011 at 9:29 PM, Nicholas Zakas nza...@yahoo-inc.com wrote:
It seems like the scoped attribute should be optional when style is used as
flow content and disallowed when used in meta content. That way, you're
adding the new functionality of limiting styles to a subtree while
Boris Zbarsky bzbar...@mit.edu schrieb am Fri, 25 Mar 2011 13:56:00
-0400:
[…]
We could argue about this of course; this is why I asked for use
cases. The use case of putting style without @scoped right at the
start of body is a good one, and I think that should be allowed...
How is that
HTML5 currently requires the scoped attribute for style elements when placed
in an area where flow content is expected. This strikes me as strange since
it's not backwards compatible with HTML 4 nor indicative of how browsers deal
with style elements as flow content today. Put quite simply,
On 3/24/11 9:29 PM, Nicholas Zakas wrote:
div
style.foo { color: red; }/style
/div
works just fine in browsers today
and the style information is applied to the entire document.
And it continues to work when they implement the proposed spec, yes.
This is considered invalid HTML5
18 matches
Mail list logo
