Open Bug 667563 Opened 14 years ago Updated 3 years ago

XUL dialog: setting the button property then getting it returns the old value

Categories

(Toolkit :: UI Widgets, defect)

defect

Tracking

()

People

(Reporter: rain1, Unassigned)

Details

STR: Start off with <dialog buttons="accept,cancel">. Then, in code: dialog.buttons = "accept"; dump(dialog.buttons); -> this prints accept,cancel.
what about dialog.setAttribute("buttons", "accept")
That doesn't trigger any changes. You need to set both the property and the attribute for it to work correctly, and that's just broken.
> You need to set both the property and the attribute for it to work correctly, and that's just broken. Unfortunately I've gotten used to doing that in most of my XUL code because there are enough places where one works and not the other.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.