Closed Bug 12270 Opened 21 years ago Closed 21 years ago
[BLOCKER] Attribute changes should use "change" when an attribute is already present
When a set attribute happens on a XUL element, and when the attribute is already present, only the nsIContent SetAttribute should be called. UnsetAttribute should never get called. This is a blocker for broadcasters/observers.
Severity: normal → blocker
Status: NEW → ASSIGNED
Component: RDF → XUL
OS: other → All
Priority: P3 → P1
Target Milestone: M10
This should be the case. I just took a look at nsRDFXULBuilder, and it seems to be behaving correctly. Is it not? Can you cough up a test case?
I didn't know if it was or not. If it is, sweet.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Fix checked in to generic builder.
david, does this work for you now? can you verify please?
Whiteboard: [99.08.26]reporter to verify → reporter to verify
no news is good news, david must be happy with the fix, marking verified.
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: phillip → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.