subtree order in slack's keyboard shortcuts pane is wrong
Categories
(Core :: Disability Access APIs, defect, P1)
Tracking
()
People
(Reporter: eeejay, Assigned: eeejay)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [mac2020_2])
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
STR:
- Open a slack instance in Firefox
- Press ctrl+/ to open keyboard shortcuts pane.
- Go to list item containing string "Move focus through messages"
Result:
List item is named "Move focus through messages up arrow key down arrow key or"
Expected:
List item should be named "Move focus through messages up arrow or key down arrow key"
Looks like slack is doing a bunch of tree stylings and mutations that mess with our insertion processing code. The insertions queue for the listitem container contains both redundant nodes, and unparented nodes. Some combination of this is causing us to reinsert children in the wrong order.
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Pushed by mzehe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4d61fef74272 (re)insert child after previous sibling, not previous insertion candidate. r=Jamie
Comment 3•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Comment on attachment 9193386 [details]
Bug 1682692 - (re)insert child after previous sibling, not previous insertion candidate. r?Jamie!
Beta/Release Uplift Approval Request
- User impact if declined: Hangs when opening the keyboard shortcuts lists in the Slack Help menu, other weird element order errors under certain circumstances.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: Bug 1681072
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Corrects tree ordering in specific circumstances and is well tested.
- String changes made/needed: None.
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Comment on attachment 9193386 [details]
Bug 1682692 - (re)insert child after previous sibling, not previous insertion candidate. r?Jamie!
Approved for 85.0b4.
Comment 6•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Description
•