El mar, 29-11-2005 a las 15:37 +0000, Ross Gardler escribió:
> Thorsten Scherler wrote:
> > Sorry, I am too busy atm to show you the commit messages regarding this
> > issue. I only have in the back of my head some committs around this
> > topic stating, what said.
> >
> > If I have this issue wrong in my head then sorry, but AFAIK
> > .codefrag literal{}
> > stands for:
> > class="codefrag" element="literal"
>
> Yes, but can 't the CSS also have:
>
> .codefrag {
> ...
> }
>
> .literal {
> ...
> }
Maybe that was the solution for the problem. ;-)
> > maybe better with a more explicit sample:
> > <span class="codefrag p">
> > gives
> > .codefrag p{}
> > which stands for
> > class="codefrag" element="p"
> >
> > which would design all elements within e.g.
> > <div class="codefrag">
> > <p>this</p>
> > </div>
> >
> > ...or am I wrong?
>
> I think you are right, but the problem is one of naming conventions. The
> class elements must not be the name of a legal HTML element in order to
> avoid the side effect that Thorsten describes.
>
> Or am *I* wrong?
>
Hmm, or it have to be defined like you describe above. Still wondering
whether all browser support class="some class otherClass" style and
display the design right.
> Ross
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
