I am trying to validate a new website I am developing against the w3.org CSS 2.1 validator and I am getting the following validation errors.
They appear to be related to RadWindow. I have created a custom skin to see if I could remove the CSS code causing the failures but no luck. Any other ideas out there?
W3C CSS Validator results for http://beta.khp.org/default.aspx (CSS level 2.1)
Sorry! We found the following errors (11)
URI : http://beta.khp.org/WebResource.axd?d=dvOjN1zPPZSPrMQOh8lxNtNXxtfzL1yxHzl7YZGYBlIAu0nibvqQVvTbHLpn3IiH0&t=633506004070402858
| 40 | div.radwindow table td.titlebar | Property -moz-user-select doesn't exist : none |
| 58 | div.radwindow td.statusbar input | Property -moz-user-select doesn't exist : none |
| 59 | div.radwindow td.statusbar input | Property text-overflow doesn't exist in CSS level 2.1 but exists in [css3] : ellipsis |
| 75 | div.radwindow td.statusbar span.statustext | Property -moz-user-select doesn't exist : none |
| 112 | div.radwindow table.titlebarcontrols em | Property text-overflow doesn't exist in CSS level 2.1 but exists in [css3] : ellipsis |
| 139 | div.radwindow.inactivewindow, div.radwindow.inactivewindow | attempt to find a semi-colon before the property name. add it |
| 139 | div.radwindow.inactivewindow, div.radwindow.inactivewindow | Property progid doesn't exist : DXImageTransform |
| 139 | div.radwindow.inactivewindow, div.radwindow.inactivewindow | Parse Error DXImageTransform.Microsoft.Alpha(opacity=70) !important; |
| 140 | opacity | Parse Error opacity: .7 !important; |
| 140 | -moz-opacity | Parse Error -moz-opacity: .7 !important; |
| 148 | -moz-opacity | Parse error - Unrecognized } |
They appear to be related to RadWindow. I have created a custom skin to see if I could remove the CSS code causing the failures but no luck. Any other ideas out there?
2 Answers, 1 is accepted
0
Hi Garry,
Let me explain in brief the CSS parser errors you are receiving upon validation and why these properties could not be removed:
1. -moz-user-select - It is a Gecko browser-specific property that makes an html element unselectable. It responds the Internet Explorer HTML attribute unselectable="on". Unfortunately, both properties are not CSS and HTML valid, but we have to use them in order to avoid element selection upon dragging;
2. text-overflow - it is a Microsoft proprietary property, and when it is used with the value "ellipsis" makes a text that is longer than its parent element be cut off with ellipsis dots ("..."). This creates a real desktop experience similar to the "real" windows behavior - when the text in the titlebar is longer than the width of the window itself, it is cut off with ellipsis dots, i.e. "Some Long Titlebar Text" will become "Some Long Titlebar..."
3. opacity is a valid CSS3 property, and you are validating against CSS2.1, that is why you get the error.
4. -moz-opacity is a Gecko proprietary property that works with older Mozilla FireFox versions. Later, with the release of Mozilla FireFox 2.5 they implemented the valid opacity property.
5. filter, and its responding DXImageTransform(...) value is a Microsoft-specific property and allows developers to use a set of handy Direct X filters and transitions on their webpages. In the case of RadWindow we implement alpha opacity via the filter property, because Internet Explorer does not support CSS opacity, and we use opacity styling for the inactive windows and the Vista "Aero" styles for certain skins.
I hope you now understand why we cannot drop these properties.
However, if you need valid CSS for your RadWindow skin, please, modify not only your custom skin by removing these properties, but also the basic CSS file of RadWindow - Window.css and do not forget register the two files in the <head>...</head> and to set the EnableEmbeddedSkins and EnableEmbeddedBaseStylesheet to false.
Please, let us know if you have ideas of replacing these properties with valid ones and we will implement these as soon as possible.
Best wishes,
Martin Ivanov
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Let me explain in brief the CSS parser errors you are receiving upon validation and why these properties could not be removed:
1. -moz-user-select - It is a Gecko browser-specific property that makes an html element unselectable. It responds the Internet Explorer HTML attribute unselectable="on". Unfortunately, both properties are not CSS and HTML valid, but we have to use them in order to avoid element selection upon dragging;
2. text-overflow - it is a Microsoft proprietary property, and when it is used with the value "ellipsis" makes a text that is longer than its parent element be cut off with ellipsis dots ("..."). This creates a real desktop experience similar to the "real" windows behavior - when the text in the titlebar is longer than the width of the window itself, it is cut off with ellipsis dots, i.e. "Some Long Titlebar Text" will become "Some Long Titlebar..."
3. opacity is a valid CSS3 property, and you are validating against CSS2.1, that is why you get the error.
4. -moz-opacity is a Gecko proprietary property that works with older Mozilla FireFox versions. Later, with the release of Mozilla FireFox 2.5 they implemented the valid opacity property.
5. filter, and its responding DXImageTransform(...) value is a Microsoft-specific property and allows developers to use a set of handy Direct X filters and transitions on their webpages. In the case of RadWindow we implement alpha opacity via the filter property, because Internet Explorer does not support CSS opacity, and we use opacity styling for the inactive windows and the Vista "Aero" styles for certain skins.
I hope you now understand why we cannot drop these properties.
However, if you need valid CSS for your RadWindow skin, please, modify not only your custom skin by removing these properties, but also the basic CSS file of RadWindow - Window.css and do not forget register the two files in the <head>...</head> and to set the EnableEmbeddedSkins and EnableEmbeddedBaseStylesheet to false.
Please, let us know if you have ideas of replacing these properties with valid ones and we will implement these as soon as possible.
Best wishes,
Martin Ivanov
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Hi Garry,
Let me explain in brief the CSS parser errors you are receiving upon validation and why these properties could not be removed:
1. -moz-user-select - It is a Gecko browser-specific property that makes an html element unselectable. It responds the Internet Explorer HTML attribute unselectable="on". Unfortunately, both properties are not CSS and HTML valid, but we have to use them in order to avoid element selection upon dragging;
2. text-overflow - it is a Microsoft proprietary property, and when it is used with the value "ellipsis" makes a text that is longer than its parent element be cut off with ellipsis dots ("..."). This creates a real desktop experience similar to the "real" windows behavior - when the text in the titlebar is longer than the width of the window itself, it is cut off with ellipsis dots, i.e. "Some Long Titlebar Text" will become "Some Long Titlebar..."
3. opacity is a valid CSS3 property, and you are validating against CSS2.1, that is why you get the error.
4. -moz-opacity is a Gecko proprietary property that works with older Mozilla FireFox versions. Later, with the release of Mozilla FireFox 2.5 they implemented the valid opacity property.
5. filter, and its responding DXImageTransform(...) value is a Microsoft-specific property and allows developers to use a set of handy Direct X filters and transitions on their webpages. In the case of RadWindow we implement alpha opacity via the filter property, because Internet Explorer does not support CSS opacity, and we use opacity styling for the inactive windows and the Vista "Aero" styles for certain skins.
I hope you now understand why we cannot drop these properties.
However, if you need valid CSS for your RadWindow skin, please, modify not only your custom skin by removing these properties, but also the basic CSS file of RadWindow - Window.css and do not forget register the two files in the <head>...</head> and to set the EnableEmbeddedSkins and EnableEmbeddedBaseStylesheet to false.
Please, let us know if you have ideas of replacing these properties with valid ones and we will implement these as soon as possible.
Best wishes,
Martin Ivanov
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Let me explain in brief the CSS parser errors you are receiving upon validation and why these properties could not be removed:
1. -moz-user-select - It is a Gecko browser-specific property that makes an html element unselectable. It responds the Internet Explorer HTML attribute unselectable="on". Unfortunately, both properties are not CSS and HTML valid, but we have to use them in order to avoid element selection upon dragging;
2. text-overflow - it is a Microsoft proprietary property, and when it is used with the value "ellipsis" makes a text that is longer than its parent element be cut off with ellipsis dots ("..."). This creates a real desktop experience similar to the "real" windows behavior - when the text in the titlebar is longer than the width of the window itself, it is cut off with ellipsis dots, i.e. "Some Long Titlebar Text" will become "Some Long Titlebar..."
3. opacity is a valid CSS3 property, and you are validating against CSS2.1, that is why you get the error.
4. -moz-opacity is a Gecko proprietary property that works with older Mozilla FireFox versions. Later, with the release of Mozilla FireFox 2.5 they implemented the valid opacity property.
5. filter, and its responding DXImageTransform(...) value is a Microsoft-specific property and allows developers to use a set of handy Direct X filters and transitions on their webpages. In the case of RadWindow we implement alpha opacity via the filter property, because Internet Explorer does not support CSS opacity, and we use opacity styling for the inactive windows and the Vista "Aero" styles for certain skins.
I hope you now understand why we cannot drop these properties.
However, if you need valid CSS for your RadWindow skin, please, modify not only your custom skin by removing these properties, but also the basic CSS file of RadWindow - Window.css and do not forget register the two files in the <head>...</head> and to set the EnableEmbeddedSkins and EnableEmbeddedBaseStylesheet to false.
Please, let us know if you have ideas of replacing these properties with valid ones and we will implement these as soon as possible.
Best wishes,
Martin Ivanov
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center