CSS-2 support, bugs, wishlists, etc.

[Matt Lavallee]

Hi folks,

 

Are there any maintained lists of "open issues", with respect to CSS-2 support in IE?

 

Also, does anyone know how to prevent IE from setting properties to their default initial value when it encounters a value it doesn't understand?  Specifically, using "position: fixed;" will nullify values set for top: and left:, if applied by a later stylesheet.

 

Thanks,

-Matt

 

[Steve Fulton]

Has MS said that IE is going to be CSS-2 compliant? If so, file a bug report
for every feature not implemented or implemented incorrectly. If every
developer did this, they might put some resources into fixing IE. Once upon
a time, they committed IE to be CSS-1 compliant. Did they ever retract this
commitment? If not you should file a bug report for CSS-1 non-compliance
(the incorrect implementation of the width property springs to mind).

As for your second problem, IE isn't resetting the top and left values, it's
ignoring them. Because it doesn't support "position:fixed", it uses the
default value for position, which is "static". Static content doesn't use
the top or left properties.

A workaround:

position:fixed!important; /* used by CSS-2 compliant clients */
position:absolute; /* used by CSS-P compliant clients */

The !important declaration stops the position:fixed rule from being
overridden by the subsequent position:absolute rule. If the client doesn't
support position:fixed, it will use the position:absolute rule

=-=-=
Steve
-=-=-

"Matt Lavallee" <mlav...@hesketh.com> wrote in message
news:OduLrt4...@cppssbbsa02.microsoft.com...

[Matt Lavallee]

"Steve Fulton" <cerbe...@hotmail.com> wrote :

> Has MS said that IE is going to be CSS-2 compliant? If so, file a bug
report
> for every feature not implemented or implemented incorrectly. If every
> developer did this, they might put some resources into fixing IE. Once
upon
> a time, they committed IE to be CSS-1 compliant. Did they ever retract
this
> commitment? If not you should file a bug report for CSS-1 non-compliance
> (the incorrect implementation of the width property springs to mind).

Actually, they've only committed to implementing as much of the CSS spec as
Developers need and request:
http://msdn.microsoft.com/workshop/standards/dude02072000.asp

I don't see that as being all too ridiculous... it's a human development
team,
and they have to make cost/benefit decisions for each iteration of the
browser.

I *would* appreciate a "cut-off" mechanism (by way of the DocType
declaration)
that would implicitly force strict interpretation, but I'm one developer in
many.

> As for your second problem, IE isn't resetting the top and left values,
it's
> ignoring them. Because it doesn't support "position:fixed", it uses the
> default value for position, which is "static". Static content doesn't use
> the top or left properties.

As I'm well aware, and was the gist of my query. The catch is that, when
truly
"cascading" stylesheets, it may be stylesheet 15 that includes the
ne'er-do-well
value, reverting IE to "static" behavior. It should, IMHO, default back to
any
earlier setting from any earlier stylesheet.

Thanks for the reply just the same,
-Matt

[Samuli Lintula]

In article <#oYrEj#SAHA.288@cppssbbsa05>, Steve Fulton wrote:
>Has MS said that IE is going to be CSS-2 compliant? If so, file a bug report
>for every feature not implemented or implemented incorrectly.

I've been trying really hard to find a place where I can file bug
reports/view already reported bugs. Do you know an address for that?

TIA

--
Samuli Lintula
samuli....@utu.fi http://users.utu.fi/saklint/
University of Turku - Department of Biochemistry