W3C CSS compliance and Editor.css

Vote:
 
We're attempting to set up our sites so that they're W3C CSS compliant. However the dummy 'property' EditMenuName which is used in Editor.css to make a style available in the HTML Editor causes the stylesheet to fail validation (see http://jigsaw.w3.org/css-validator for details). Would it be possible to still use the EditMenuName dummy property if it was commented out? For instance: /* EditMenuName: Heading 1; */ In that way, the stylesheet would still pass W3C CSS validation, but we could still mark styles to be available in the Editor.
#18704
Mar 25, 2008 19:45
Vote:
 
We have to investigate further on this, to see how it can be done in a W3C CSS compliant way (Id #29487 in our issue database). Thanks for the input!
#18931
Mar 25, 2008 19:45
Vote:
 
You could allow the administrator to define a config-file for the HTML-editor and move this information into that file. I think that would be much cleaner for the developers also. If it isn't already it should be possible to define the editor css (and config-file) for each template. We might use different css-files with different templates.
#18932
Mar 25, 2008 19:45
Vote:
 
The easy solution is to separate your CSS into two files. One that you include on your page and one for the editor which imports the first one and adds the EditMenuName-statements. Problem solved.
#18933
Mar 25, 2008 19:45
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.