Open
Bug 1514141
Opened 5 years ago
Updated 2 years ago
Richlistbox breaks selection of richlistitems if their binding is not yet attached
Categories
(Toolkit :: UI Widgets, defect, P3)
Toolkit
UI Widgets
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox64 | --- | unaffected |
firefox65 | --- | unaffected |
firefox66 | --- | fix-optional |
People
(Reporter: mak, Unassigned)
References
Details
(Keywords: regression)
If you add a richlistitem to a richlistbox, and set selectedIndex before the richlistitem binding is attached, the selection of that richlistitem is broken forever, because you end up setting a "selected" expando the overrides the selected property of the binding. Since the richlistbox properly has its binding, using its methods should not corrupt the children.
Updated•5 years ago
|
Priority: -- → P3
Comment 1•5 years ago
|
||
I am attempting to triage this bug, but I do now know how to reproduce it. It needs the version flags on which it occurs and the ones that are unaffected. It probably only needs the firefox66 (latest Nightly), firefox65 (latest Beta) and firefox64 (the latest release version). Do you know if it occurs on these 3 main versions of Firefox? If not, can you provide me with some sort of test case (or some detailed steps to reproduce) that I could use to test the needed versions? Thank you for your contribution!
Flags: needinfo?(mak77)
Reporter | ||
Comment 2•5 years ago
|
||
This is a more technical bug, that may not be directly exposed to the user (or can be workarounded anyway). It is the underlying cause of bug 1513469, the urlbar has been broken from 2018-12-11 to 2018-12-14 (extremes included). The current urlbar workarounded this bug by issuing a dispatchToMainThread, that allows the binding to be attached before proceeding. I'm setting the flags accordingly.
Comment 4•5 years ago
|
||
Oups, sorry about the typo.
Comment 5•5 years ago
|
||
Happy to take a patch for 66 here; I'm marking this fix-optional to remove it from triage since it has a priority assigned.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•