W3C home > Mailing lists > Public > www-style@w3.org > April 2008

RE: [cssom-view] small update

From: Mike Wilson <mikewse@hotmail.com>
Date: Mon, 21 Apr 2008 15:30:39 +0200
Message-ID: <BAY116-DAV1EAA92DC924F7D6134A20A4E10@phx.gbl>
To: "'Www-style'" <www-style@w3.org>
Message-ID: <009801c8a3b3$e4038ad0$0a01a8c0@mikedeskxp>

> >> >> Do you think this section
> >> >> http://dev.w3.org/csswg/cssom-view/#background
> >> >> is clear enough on that or do you want me to add a 
> >> >> sentence saying
> >> >> explicitly that it doesn't match current implementations?
> >> >
> >> > If chosing this path I would like to see comments in each
> >> > relevant section, mentioning heritage and compatibility, f ex:
> >>
> >> Why?
> >
> > Why not?
> 
> It's no longer relevant in the future.

But it's very relevant as long as we have a lot of old browsers
around (<=IE7, <=FF2). But, anyway:

What I am seeking is to service the reader that wants to analyze
if the spec is making Wise Decisions.
Currently, a reader that wants to do this for the offset* properties
will have to do his own reverse-engineering and search for 
incompatibilities, and then weigh if they are acceptable or not. This
will probably not happen.
Having the information presented (per feature) will assist the 
reader and this will lead to better feedback on the spec.

If this kind of information doesn't fit in the way you want to write
your spec, then fine. But I think this information needs to be made
available in some way, f ex in a separate document as I suggested, so
the reader has the critical information at hand. But I have no strong
opinion on how the information is made available as long as it is
easily found by a person reviewing the cssom spec.

Best regards
Mike Wilson
Received on Monday, 21 April 2008 13:31:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:05 GMT