- From: Ian Hickson <ian@hixie.ch>
- Date: Sun, 15 Dec 2002 00:24:59 +0000 (GMT)
- To: Tantek Çelik <tantek@cs.stanford.edu>
- Cc: "www-style@w3.org" <www-style@w3.org>
On Sat, 14 Dec 2002, Tantek Çelik wrote:
> On 12/14/02 4:07 AM, "Ian Hickson" <ian@hixie.ch> wrote:
>
> I had not thought there would be *any* reason to treat this
> differently in quirks vs. strict mode.
Yeah, I was quite surprised to find it failing in quirks mode too.
From a black-box QA point of view, it really feels like IE6's quirks mode
is the IE5.5 engine, and the strict mode is a separate one...
> We'll fix Tasman to comply with this interpretation - could you
> suggest the specific errata for CSS1 & 2 to clarify the interpretation
> in the specs?
Well, my argument is that it doesn't require clarification. ;-)
The easiest way might be to just change the example in the 4.1.6 Blocks
section of CSS 2.1 from:
{ causta: "}" + ({7} * '\'') }
...to:
{ causta { "}" + ({7} * '\'') } }
...or some such.
The more I read 4.1.6, the less I can work out how else it could be
interpreted. Maybe at the end of 4.1.8 "Declarations and properties", we
could add "Note that the parsing rules for generic blocks all apply to
declaration blocks as well. Foor instance if an opening brace is found in
an unexpected place, it does still delimit the start of the block.".
Since you thought there was an alternative interpretation, what do _you_
think should be changed? :-)
--
Ian Hickson )\._.,--....,'``. fL
"meow" /, _.. \ _\ ;`._ ,.
http://index.hixie.ch/ `._.-(,_..'--(,_..'`-.;.'
Received on Saturday, 14 December 2002 19:25:05 UTC