W3C CSS Validator -moz-inline-block, zoom

[Phil C]

Hi, have put a Q1 2008 Treeview in and all great, however W3C CSS Validator fails on the following, maybe there is a workaround otherwise please eradicate from next releases as full validation is a real bonus and can't display the logo otherwise. Phil.

46	.RadTreeView div.rtIn	Value Error : display -moz-inline-block is not a display value : -moz-inline-block
77	.RadTreeView .rtSp	Value Error : display -moz-inline-box is not a display value : -moz-inline-box
93	.RadTreeView .rtPlus, .RadTreeView .rtMinus	Value Error : display -moz-inline-box is not a display value : -moz-inline-box
104	.RadTreeView .rtTop, .RadTreeView .rtMid, .RadTreeView .rtBot, .RadTreeView .rtUL	Property zoom doesn't exist : 1
117	.RadTreeView .rtLoadingBefore, .RadTreeView .rtLoadingAfter	Value Error : display -moz-inline-box is not a display value : -moz-inline-box
166	.RadTreeView_rtl .rtLI, .RadTreeView_rtl .rtIn	Property zoom doesn't exist : 1

[Alex Gyoshev]

Hello Phil C,

Unfortunately, the validation errors are caused by proprietary properties (namely Mozilla's and Microsoft's) which allow the usage of properties that are not officially supported. Having that said,

1. We need to use proprietary CSS properties in order to support the control's required functionality;
2. According to the W3C CSS specification, user agents are allowed to introduce proprietary CSS properties;
3. The HTML validator does not work with point (2) in mind, so pages don't validate

If you insist on having a validating web application, you can set the EnableEmbeddedSkins and EnableBaseStyleSheet properties to false and register the CSS files manually for the common browsers. If you detect the User Agent to be a validator, simply do not register those CSS files and the page will validate. However, this is just tricking the validator. After all, we make websites for people, not validators.

Best wishes,
Alex
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Phil C]

Fair enough Alex, it's all a pain to support buggy browsers let alone validate-failed custom CSS properties, maybe W3C should set these as a warning then, not a failure.

Unfortunately the people we design for include the clients who like to see full CSS Validation logo, but I get your point. Phil.