Closed
Bug 911078
Opened 10 years ago
Closed 5 years ago
Australis: (write tests to) check that showInPrivateBrowsing and panel wide widget rearranging code are happy with each other.
Categories
(Firefox :: Toolbars and Customization, defect)
Firefox
Toolbars and Customization
Tracking
()
RESOLVED
INVALID
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [Australis:P5])
This is a somewhat theoretical problem, I suppose, as it's about the case where: - Someone uses private browsing mixed with normal browsing, and opens the panel - Someone uses widgets that specify showInPrivateBrowsing = false (is this the jetpack default? I hope not...) - Someone adds those to the panel before any wide widgets This will make things a bit sadfaces where the re-arranging code is concerned. I *think* the practical consequence right now is that wide items will get moved (possibly in multiple steps) to be before "public browsing only" widgets, as there will always be a window in which the wide widget is unhappy with the number of items that come before it (as this will be different in different windows). I think this is OK, but I wanted to check that we're OK with this and/or want to do something else.
Reporter | ||
Comment 1•10 years ago
|
||
I fixed this to only take 1 step in bug 885579. However, there are currently no tests for this, and my manual testing was also minimal. We should probably doublecheck this before we release, although we don't need to do that before we land on m-c as this is a pretty edgy edge-case.
Summary: Australis: showInPrivateBrowsing causes problems for panel wide widget rearranging code → Australis: (write tests to) check that showInPrivateBrowsing and panel wide widget rearranging code are happy with each other.
Updated•9 years ago
|
Whiteboard: [Australis:M?][Australis:P5] → [Australis:P5]
Reporter | ||
Comment 2•5 years ago
|
||
We got rid of wide widgets and the old panel stuff.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•