On 2005-Jan-05, at 04:24, Hussein Shafie wrote: > David Mundie wrote: >> I am not a W3C recommendations lawyer, but I fail to see what >> inheritance has to do with this. Inheritance comes into play when a >> property is not set on an element, and the computed value from the >> parent is used instead. But in the case at hand, the display property >> is *explicitly* set to block, so there's no issue of inheritance; >> according to the section you cite, if the display property has the >> value block, it should cause the element to generate a principal >> block box, end of story. I see nothing in the recommendation that >> says a value of inline on an ancestor element *overrides* an >> explicitly-set value of block on the child element, which is the way >> XMLEditor behaves. > > Sorry I didn't understand your point. Please consider this behavior as > a limitation of XXE: the editor simply cannot cope with blocks > contained inside inlines.
Fair enough. I'm willing to put up with quite a few limitations if it preserves XXE's high performance. - dam
