- From: Ben Boyle <benjamins.boyle@gmail.com>
- Date: Wed, 30 May 2007 21:02:09 +1000
- To: "Maciej Stachowiak" <mjs@apple.com>
- Cc: "Henri Sivonen" <hsivonen@iki.fi>, "Daniel Glazman" <daniel.glazman@disruptive-innovations.com>, "David Hyatt" <hyatt@apple.com>, "Preston L.Bannister" <preston@bannister.us>, "Dan Connolly" <connolly@w3.org>, "public-html@w3.org WG" <public-html@w3.org>
Will existing (non-HTML5 aware) UAs ignore that "scoped" attribute and treat "scoped style" as they currently do <style>? Speaking as an author, it sounds like it will be hard to reliably use scoped style whilst supporting legacy UAs ... I see <iframe> in HTML5. How does that relate to this issue of "scoping"? If I'm reading this list correctly, it seems the key point is HTML documents that are built from multiple sources... and style @scoped is the proposal for attaching local style to these snippets? That seems very similar to the concept of an iframe... (I'm trying to understand the real purpose/need behind scoped style) On 5/30/07, Maciej Stachowiak <mjs@apple.com> wrote: > > > On May 30, 2007, at 1:11 AM, Henri Sivonen wrote: > > > On May 29, 2007, at 23:07, Maciej Stachowiak wrote: > > > >> For purposes of document conformance, the new <style scoped> > >> feature in the HTML5 draft would be allowed anywhere in the > >> document - this is already true in the draft. > > > > Actually, in the current draft <style scoped> is only allowed at > > the start of article, aside, div, and section elements. > > My mistake. This would make Dave's proposed change to its processing > a relatively smaller change for conforming documents, but possibly > also less important, since the only backwards style application would > be up to the parent, and even then only if one of the contained rules > applies. (I have no strong opinion on it either way.) > > Cheers, > Maciej > > >
Received on Wednesday, 30 May 2007 21:02:03 UTC