Glad to help. I agree, colorizing base on attribute value is a better idea.
Actually suppressing content in the editor is inviting confusion on the part of
the author :)
Looking at your example, I don't understand the second * in
*[vendor*="value"]{background-color:blue}, tho I don't know much CSS2.
*[vendor="value"]{background-color:blue} does work for me as does
*[vendor~="value"]{background-color:blue}.
David
> -----Original Message-----
> From: Damien Fitzpatrick [mailto:Damien.Fitzpatrick at Ephox.com]
> Sent: Tuesday, March 09, 2004 7:40 PM
> To: David Cramer (Tech Pubs); 'xmleditor-support at xmlmind.com'
> Subject: RE: [XXE] Support for profiling
>
>
> Thanks for the tip David. I have created a CSS to colour
> code my XML now so that the profiled content appears
> differently depending on what the relevant profiled
> attributes' values are. Just for the record I added a new
> stylesheet to the XMLMind Docbook stylesheets which used
> attribute selectors to colour the profiled sections of the
> document differently depending on what subset of the
> documentation they appeared in.
>
> For the moment I am actually finding it more useful to make
> all my content visible and then change the background-color
> style depending on the profile of the section. Though it
> would also be useful to be able to show and hide sections
> with different profiles at will like David has suggested here.
>
> Finally, I would like to report what I think is a bug within
> the CSS support of XMLMind. It appears that with the
> attribute selectors you cannot use the "*" or "^" selectors
> (there may be others that don't work but these are the only
> ones I tried). For example, the following CSS listing caused
> XMLMind to throw an error: *[vendor*="value"]{background-color:blue}.
>
> Regards,
> Damien
>
