Loss of reference when changing element attribute using setAttribute() ?

NEW
Unassigned

Status

()

--
minor
17 years ago
9 years ago

People

(Reporter: sergi20m, Unassigned)

Tracking

Trunk
Future
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
Using the setAttribute() method to set an existent attribute causes the loss of
element's reference or something, because when serializing the elements
attributes through the attributes[] array, the changed attribute appears twice,
one with the old value and again with the new changed attribute, and if there
were other attributes in the element, they do not appear when serializing the
attributes[] array after doing the setAttribute.

testcase: 
http://www.mans-hq.net/XUL/wrongTestSerialize.xul

testcase with a workaround: 
http://www.mans-hq.net/XUL/rightTestSerialize.xul
(Reporter)

Updated

17 years ago
Summary: Lost of reference when changing element attribute using setAttribute() ? → Loss of reference when changing element attribute using setAttribute() ?

Updated

17 years ago
Severity: major → minor
Target Milestone: --- → Future
to XUL
Assignee: jaggernaut → hyatt
Status: UNCONFIRMED → NEW
Component: XP Toolkit/Widgets → XP Toolkit/Widgets: XUL
Ever confirmed: true
QA Contact: jrgm → shrir

Comment 2

17 years ago
There's a missing '>' in the second attachment:

xmlns:xul = "http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
<xul:script>
(Reporter)

Comment 3

17 years ago
Fixed missing '>'.

Thanx ;)

Updated

11 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets

Updated

9 years ago
Assignee: hyatt → nobody
You need to log in before you can comment on or make changes to this bug.