Rafael wrote: > A link is really useful in these cases. If you can, strip down your > HTML & CSS to simply things.
Can't give you urls, I'm afraid (secure server). In any case, the problem is entirely generic. I have completely stripped down everything, to the point where the computed style for headers and legends is identical. However the type of 'display' applied to legends is intrinsically weird. Remember that by default they sit /inside/ the border of their containing frameset. My particular problem is that they seem to retain inline properties even when set as block. A computed 100% width will still end up as the minimum width required by the content. The only way I can find to extend the box is by applying fixed padding, ie values in px or ems. Snadden Tim wrote: >> And I want legends to act like headers.> > > Legends are very tricky to style. I found that the best way to get > control was to add a span inside and style that. Extra markup is > obviously not ideal but it appears to be the only practical solution to > get real control over rendering of legends. This is a generically helpful way of dealing with obtuse objects, but actually it doesn't help in this circumstance. The misbehaving bounding box of the legend will still clip the contents, whatever they may be. The problem is that the legend cannot be relied upon to behave based on the metrics around it. I am treating this as a case of "systematic introduction of unsemantic markup and highly protracted styles vs. javascript" (javascript always wins, it's CSS4). Regards, Barney ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
