Closed Bug 240991 Opened 21 years ago Closed 6 years ago

document.write in external javascript inside div with xbl binding gives problems with content

Categories

(Core :: XBL, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: martijn.martijn, Unassigned)

References

()

Details

(Keywords: testcase)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040418 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040418 Firefox/0.8.0+ See: http://home.hccnet.nl/m.wargers/test/mozilla/xblexternaljsbug/t.htm http://home.hccnet.nl/m.wargers/test/mozilla/ I have a div class="test" with a -moz-binding: <div class="test"><script src="test.js"></script></div> Inside the div there is a script which does a document.write('external data'); Maybe you don't see the problem directly. Then do a shift-reload or try it locally. Reproducible: Always Steps to Reproduce: 1.See testcase 2. 3. Actual Results: I did see: external datagg ggexternal data ggexternal data You should see four times "external datagg" Expected Results: I should see: external datagg external datagg external datagg external datagg You should see four times "external datagg"
hyatt should not be default assignee for xbl bugs any longer, but who is willing to take that job? /be
Assignee: hyatt → nobody
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 240908
Well, _if_ we had component watching I'd say the default assignee should be nobody and some people should watch the component. If we had a useful QA contact, similar. As it is... assignee should probably still be nobody, and QA should cc relevant people as needed....
Attached file Testcase
Reporter: did this work before, as you mention in the marquee bug?
Original testcase URL: http://home.hccnet.nl/m.wargers/test/mozilla/xblexternaljsbug/t.htm Well, the parts that say "ggexternal data" are due to the code at http://lxr.mozilla.org/seamonkey/source/content/xbl/src/nsBindingManager.cpp#1365 -- this does not handle proper relative ordering of anonymous and non-anonymous content. In fact, it really can't, as far as I can see, given the informatioon XBL currently keeps around. See the XXX comment at http://lxr.mozilla.org/seamonkey/source/content/xbl/src/nsBindingManager.cpp#1432 I have no idea offhand why the fourth div isn't even showing up. No assertions in a debug build that I can see, though....
Reply to comment 4: no, this testcase did not work before the fix to bug 167224. I don't think this ever worked. I think this bug has something to do with causing bug 240908. However I'm not sure, because the circumstances are not exactly the same, I think.
Keywords: testcase
QA Contact: ian → xbl
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

XBL is now disabled in Firefox (Bug 1583314) and is in the process of being removed from Gecko (Bug 1566221), so closing bugs requesting changes to its implementation as wontfix.

Status: REOPENED → RESOLVED
Closed: 8 years ago6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: