Closed
Bug 303625
Opened 19 years ago
Closed 19 years ago
nsXFormsSubmissionElement::LoadReplaceAll uses wrong document
Categories
(Core Graveyard :: XForms, defect)
Core Graveyard
XForms
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Biesinger, Assigned: allan)
References
()
Details
(Keywords: fixed1.8.0.5, fixed1.8.1)
Attachments
(1 file)
1.25 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
The code gets the ownerDocument and a container from that (in order to load a new document there). It seems to me like the code really wants to use the current document (GetCurrentDoc()) of the node.
Assignee | ||
Comment 1•19 years ago
|
||
(In reply to comment #0) > The code gets the ownerDocument and a container from that (in order to load a > new document there). > > It seems to me like the code really wants to use the current document > (GetCurrentDoc()) of the node. Nobody ever did anything about this. Why should we use GetCurrentDoc() instead? Mind you that it is an XTF element.
![]() |
||
Comment 2•19 years ago
|
||
If the element comes from an XBL binding (could it?) then the owner doc and current doc would be different in XBL2 -- the owner doc would be the XBL binding document while the current doc would be the bound document. More to the point, anything involving presentation (including containers) should be using the current document, since it's depending on messing with the "view" the element is in, not where the element hails from.
Assignee | ||
Comment 3•19 years ago
|
||
(In reply to comment #2) > If the element comes from an XBL binding (could it?) No. > then the owner doc and current doc would be different in XBL2 -- the owner doc > would be the XBL binding document while the current doc would be the bound > document. > > More to the point, anything involving presentation (including containers) > should be using the current document, since it's depending on messing with the > "view" the element is in, not where the element hails from. But the submission element has no visual representation.
![]() |
||
Comment 4•19 years ago
|
||
> No. So if XBL anonymous content includes a submission element nothing will happen? What if XBL anonymous content includes a complete XForms form? > But the submission element has no visual representation. That's a matter of its CSS display type, no?
Assignee | ||
Comment 5•19 years ago
|
||
(In reply to comment #4) > > No. > > So if XBL anonymous content includes a submission element nothing will happen? > What if XBL anonymous content includes a complete XForms form? Ah, sorry, understood that the wrong way around. submission's not going to be very happy unless it's a child of a model, but that said, you could stash it inside XBL anonymous content, yes. > > But the submission element has no visual representation. > > That's a matter of its CSS display type, no? Hmmm, it inherits from nsIXTFGenericElement which iirc should have no visual representation.
![]() |
||
Comment 6•19 years ago
|
||
> which iirc should have no visual representation.
It's just treated as "display: none !important" in the UA style sheet, basically. Except hardcoded in C++ in a hacky way.
But back to the XBL anonymous content issue. Would you be wanting to do the load in the XBL binding document, or the document the binding is attached to? That's the line between GetOwnerDoc and GetCurrentDoc.
Assignee | ||
Updated•19 years ago
|
Assignee: aaronr → xforms
Assignee | ||
Comment 7•19 years ago
|
||
(In reply to comment #6) > > which iirc should have no visual representation. > > It's just treated as "display: none !important" in the UA style sheet, > basically. Except hardcoded in C++ in a hacky way. > > But back to the XBL anonymous content issue. Would you be wanting to do the > load in the XBL binding document, or the document the binding is attached to? > That's the line between GetOwnerDoc and GetCurrentDoc. (oops, this disappeared in my bugmail) We want to load in the document that the binding is attached to.
Assignee | ||
Comment 9•19 years ago
|
||
![]() |
||
Updated•19 years ago
|
Attachment #223753 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 10•19 years ago
|
||
Fixed on trunk.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
OS: Windows XP → All
Hardware: PC → All
Resolution: --- → FIXED
Whiteboard: xf-to-branch
Assignee | ||
Updated•19 years ago
|
Keywords: fixed1.8.0.5
Assignee | ||
Updated•19 years ago
|
Keywords: fixed1.8.1
Assignee | ||
Updated•19 years ago
|
Whiteboard: xf-to-branch
![]() |
||
Updated•18 years ago
|
Flags: blocking1.9a2?
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•