Bug 497519 part 2. Only do special handling for legends whose content parnt is an HTML fieldset. bzbarsky
This commit is contained in:
@@ -3656,11 +3656,15 @@ nsCSSFrameConstructor::FindHTMLData(nsIContent* aContent,
|
||||
(aParentFrame->GetType() != nsGkAtoms::fieldSetFrame &&
|
||||
aParentFrame->GetStyleContext()->GetPseudoType() !=
|
||||
nsCSSAnonBoxes::fieldsetContent) ||
|
||||
!aContent->GetParent() ||
|
||||
!aContent->GetParent()->IsNodeOfType(nsINode::eHTML) ||
|
||||
aContent->GetParent()->Tag() != nsGkAtoms::fieldset ||
|
||||
aStyleContext->GetStyleDisplay()->IsFloating() ||
|
||||
aStyleContext->GetStyleDisplay()->IsAbsolutelyPositioned())) {
|
||||
// <legend> is only special inside fieldset frames, but for floated or
|
||||
// <legend> is only special inside fieldset, check both the frame tree
|
||||
// parent and content tree parent due to XBL issues. For floated or
|
||||
// absolutely positioned legends we want to construct by display type and
|
||||
// not do special legend stuff
|
||||
// not do special legend stuff.
|
||||
// XXXbz it would be nice if we could just decide this based on the parent
|
||||
// tag, and hence just use a SIMPLE_TAG_CHAIN for legend below, but the
|
||||
// fact that with XBL we could end up with this legend element in some
|
||||
|
||||
Reference in New Issue
Block a user