Ken Lassesen
Top achievements
Rank 2
Rank 2
Ken Lassesen
asked on 06 Jul 2010, 02:44 PM
I have been using the Qualidator SiteAnalyzer (German Company) to get really strict sites -- unfortunately, the only item used that I cannot get to pass is connected to Telerik Grid. The problems are preceded by "Spaghetti" below, indicating spaghetti mockup.
You can download their free version of their tool at http://www.qualidator.com.
I suspect that the best solution (because of browser compatibility issues) would be to conditionally move these items to css (class) depending on the browser.
| <table |
| Spaghetti Markupcellspacing="0" class="rgMasterTable Css Class" |
| Spaghetti Markupborder="0" id="MainContent_Summary_65af65eb-72ff-4258-b047-6b6e5f742b5f_ctl00" summary="Listing of transactions recorded against Child Account #4." |
| style="Spaghetti Markupwidth:100%;table-layout:auto;empty-cells:show;"> |
1 Answer, 1 is accepted
0
Hi Ken,
The provided code snippet is valid XHTML 1.0 Transitional markup.
We agree that using external CSS styles is better than using inline styles, but in some cases it is important to ensure that a certain style will be applied in all cases, no matter what the skin settings are (e.g. Skin turned off). There are also scenarios in which different browsers require different styles and moving such styles to external CSS files will require CSS hacks - something, which should be avoided even more. Finally, external CSS styles are more easily overridden from custom application styles, compared to inline styles.
On a side note, removing all inline styles and moving them to the external CSS will tend to increase the control's complexity and reduce maintainability from developer's point of view. Inline styles are something which generally "does not exist".
Surely, we always keep in mind the HTML/CSS best practices and apply them in the process of control evolution and improvement.
Best wishes,
Dimo
the Telerik team
The provided code snippet is valid XHTML 1.0 Transitional markup.
We agree that using external CSS styles is better than using inline styles, but in some cases it is important to ensure that a certain style will be applied in all cases, no matter what the skin settings are (e.g. Skin turned off). There are also scenarios in which different browsers require different styles and moving such styles to external CSS files will require CSS hacks - something, which should be avoided even more. Finally, external CSS styles are more easily overridden from custom application styles, compared to inline styles.
On a side note, removing all inline styles and moving them to the external CSS will tend to increase the control's complexity and reduce maintainability from developer's point of view. Inline styles are something which generally "does not exist".
Surely, we always keep in mind the HTML/CSS best practices and apply them in the process of control evolution and improvement.
Best wishes,
Dimo
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items