Closed
Bug 341943
Opened 19 years ago
Closed 11 years ago
Setting element properties in different functions called from request handler
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: GICodeWarrior, Unassigned)
References
()
Details
Attachments
(1 file)
1.26 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
The source at that URL should give a good example. Basically I am getting an element using getElementById in two different places. This normally works, but if I get it inside a XmlHttpRequest handler, do something to it, then call another function that gets the same element using getElementById and tries to do something to it, the second change doesn't work...
Reproducible: Always
Steps to Reproduce:
1. Make a XmlHttpRequest
Inside the request handler:
2. Get an element using getElementById.
3. Set a property of that element (innerHTML in this example)
4. Call another function
Inside the other function:
5. Get the exact same element using getElementById
6. Edit a (different) property on that element
Actual Results:
The second property change doesn't work.
Expected Results:
The property change should work.
There is a test case here:
http://www.csh.rit.edu/~gicode/projects/firefox/test.htm
If you click on "CLICK HERE" another "CLICK HERE" should appear below it.
If you download it and try it on your machine you can uncomment line 34 and comment line 35. This will bypass the function call and show how it should work.
Updated•15 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 2•11 years ago
|
||
Reporter's demo works fine in Firefox now :)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•