Forum Bugs

prince-bookmark-level bug or normal?

JohnClarke
I would think that I could do something like:
div.manualbookmark{
  bookmark-target: attr(id);
}
div.manualbookmark .one{
  prince-bookmark-level: 1;
}
div.manualbookmark .two{
  prince-bookmark-level: 2;	
}
div.manualbookmark .three{
  prince-bookmark-level: 3;	
}

would cascade the attr(id) into the individual elements: .one, .two, .three. This does not seem to work that way. I had to explicitly declare the property for each element class.
div.manualbookmark{
}
div.manualbookmark .one{
  prince-bookmark-level: 1;
  bookmark-target: attr(id);
}
div.manualbookmark .two{
  prince-bookmark-level: 2;	
  bookmark-target: attr(id);
}

div.manualbookmark .three{
  prince-bookmark-level: 3;	
  bookmark-target: attr(id);
}

Is this normal behaviour? I have no idea, but thought the first section of CSS was more intuitive. -John

John Clarke
Cornerstone Systems Northwest Inc.

mikeday
This is expected behaviour, as none of the bookmark properties are inherited by child elements. However, if you always have a single bookmark inside the div.manualbookmark, you could rewrite the first rule like this:
div.manualbookmark * {
    bookmark-target: attr(id)
}

(Note that this applies to all the elements within the div).