CSS strict implementation (Quick Check)

[Bob90]

Hi all,

Any help would be great. It's hard to find good info on strict css; well for me anyway

Whats wrong with the below code? Anything?

.skin0{
 position: absolute;
 cursor: default;
 z-index: 50;
 visibility: hidden;
}

[Twey]

No, nothing, although you might want to insert a space before the {: I think there's a bug that occasionally affects one of the earlier versions of IE if you don't.

[Bob90]

How the hell do you know stuff like that!
Thanks anyway.

[Bob90]

Its actually part of a bigger problem, but I didn't want to bog anyone down with my stupidity.

I just changed to a strict web page and I'm having problems.

Any help as to why my right-click menu doesn't work?

Does strict also apply to javascript?

Know any decent references for strict authoring?

Thanks

[jscheuer1]

Changed to strict from what? Transitional or quirks? DOCTYPE does affect javascript. One of the two most common ways is that you may be required to specify units for pixels in about any DOCTYPE, also the way IE gets the body element in certain scripting situations changes when changing from quirks to a valid DOCTYPE.

Differing DOCTYPE's will cause markup to render differently in many cases. Where javascript is dependant upon markup, this can mess up a script.

Additionally, anything that is invalid in a given DOCTYPE, whether it is hard coded or created by a script can cause problems.

[Bob90]

Thanks for the pixek thing. As fir the rest i will work through my code and sort it out (I went from transitional)

[mburt]

If you use a DOCTYPE, use the w3c validator to check it. It will tell (mostly) what's wrong and about where to find it on your page:
http://validator.w3.org/

[jscheuer1]

If you use a DOCTYPE, use the w3c validator to check it. It will tell (mostly) what's wrong and about where to find it on your page:
http://validator.w3.org/

Generally that will only help to fix hard coded HTML and can often generate erroneous error reports for on page scripts as well as miss errors in any script generated HTML.

It is still a good idea but, best to know its limitations.

[Twey]

can often generate erroneous error reports for on page scripts

Not erroneous. The things the validator reports are indeed invalid.

[jscheuer1]

Not erroneous. The things the validator reports are indeed invalid.

Not for on page scripts. It will erroneously report that tags which are 'not open' are being closed. However, since these tags are themselves within script tags, they are not tags, they are code. Or, if looked at as the strings that they are, usually do have opening tags that the validator is ignoring. Either way it is a goof of the validator.

This is why scripts generally should be made external for validation.