Closed
Bug 888817
Opened 11 years ago
Closed 11 years ago
Back-button mis-styled after customizing with multiple windows because other windows' currentset attributes aren't updated
Categories
(Firefox :: Toolbars and Customization, defect)
Tracking
()
RESOLVED
FIXED
Firefox 28
People
(Reporter: fx4waldi, Assigned: Gijs)
References
(Blocks 1 open bug)
Details
(Whiteboard: [Australis:M8][Australis:P3])
Attachments
(3 files, 1 obsolete file)
63.45 KB,
image/png
|
Details | |
5.25 KB,
patch
|
mconley
:
review+
|
Details | Diff | Splinter Review |
4.57 KB,
patch
|
mconley
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:25.0) Gecko/20130630 Firefox/25.0 (Nightly/Aurora)
Build ID: 20130630040203
Steps to reproduce:
1. Open window
2. Open second window
3. In the first window open customization mode
4. Move the back/forward buttons to another place
5. Close customization mode
Actual results:
In the first window buttons is normal.
In other windows buttons are styles such as if they were next to Location Bar
Blocks: australis-cust
Component: Untriaged → Theme
Whiteboard: [Australis:M?]
Version: 25 Branch → Trunk
Comment 1•11 years ago
|
||
Sounds like the customization code fails to update the currentset attribute in all windows.
Component: Theme → Toolbars and Customization
Summary: Circular the back button after customizing at multiple window → Circular the back button after customizing at multiple window (currentset attribute not updated reliably?)
Updated•11 years ago
|
Summary: Circular the back button after customizing at multiple window (currentset attribute not updated reliably?) → Circular back button out-of-place after customizing in multiple windows (currentset attribute not updated reliably?)
Comment 2•11 years ago
|
||
Does bug 755598 avoid this? Or is there just a more fundamental issue?
Assignee | ||
Comment 3•11 years ago
|
||
I can reproduce this, so confirming. Dao's comment #1 looks to be spot-on AFAICT.
(In reply to Justin Dolske [:Dolske] from comment #2)
> Does bug 755598 avoid this? Or is there just a more fundamental issue?
Yes, it will avoid the symptom, but we should probably update the attribute correctly everywhere to avoid issues with our legacy/add-on support. Marking P3 because of theoretical compat impact, assuming 755598 gets fixed and avoids the more easily visible issue here.
Assignee: nobody → gijskruitbosch+bugs
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Summary: Circular back button out-of-place after customizing in multiple windows (currentset attribute not updated reliably?) → Back-button mis-styled after customizing with multiple windows because other windows' currentset attributes aren't updated
Whiteboard: [Australis:M?] → [Australis:M?][Australis:P3]
Assignee | ||
Comment 4•11 years ago
|
||
This WFM in a quick test, and also makes more sense to me than our current implementation. What do you think?
Attachment #776376 -
Flags: review?(mconley)
Comment 5•11 years ago
|
||
Comment on attachment 776376 [details] [diff] [review]
Patch v1
Review of attachment 776376 [details] [diff] [review]:
-----------------------------------------------------------------
This looks like it should be relatively painless to write a regression test for. Would you mind giving that a shot when you have a minute? I can review that separately.
Attachment #776376 -
Flags: review?(mconley) → review+
Assignee | ||
Comment 6•11 years ago
|
||
Good point! Here's a test.
Attachment #776425 -
Flags: review?(mconley)
Comment 7•11 years ago
|
||
Comment on attachment 776425 [details] [diff] [review]
test that currentset should be updated when items are moved,
Review of attachment 776425 [details] [diff] [review]:
-----------------------------------------------------------------
::: browser/components/customizableui/test/browser_888817_currentset_updating.js
@@ +15,5 @@
> + let navbar = document.getElementById(CustomizableUI.AREA_NAVBAR);
> + let personalbar = document.getElementById(CustomizableUI.AREA_BOOKMARKS);
> + let navbarCurrentset = navbar.getAttribute("currentset") || navbar.currentSet;
> + let personalbarCurrentset = personalbar.getAttribute("currentset") || personalbar.currentSet;
> +
It might be worth opening up another window and ensuring that the currentset is updated there too.
Assignee | ||
Comment 8•11 years ago
|
||
Alright, let's also open another window.
Attachment #776435 -
Flags: review?(mconley)
Assignee | ||
Updated•11 years ago
|
Attachment #776425 -
Attachment is obsolete: true
Attachment #776425 -
Flags: review?(mconley)
Comment 9•11 years ago
|
||
Comment on attachment 776435 [details] [diff] [review]
test that currentset should be updated when items are moved,
Review of attachment 776435 [details] [diff] [review]:
-----------------------------------------------------------------
LGTM!
Attachment #776435 -
Flags: review?(mconley) → review+
Assignee | ||
Comment 10•11 years ago
|
||
Whiteboard: [Australis:M?][Australis:P3] → [Australis:M8][Australis:P3][fixed-in-ux]
Assignee | ||
Comment 11•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [Australis:M8][Australis:P3][fixed-in-ux] → [Australis:M8][Australis:P3]
Target Milestone: --- → Firefox 28
You need to log in
before you can comment on or make changes to this bug.
Description
•