Closed
Bug 1087227
Opened 10 years ago
Closed 5 months ago
Panel container shows surrounding border after multiple Windows theme changes
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: pauly, Unassigned)
References
Details
(Whiteboard: [UX bug])
Attachments
(1 file)
114.85 KB,
image/png
|
Details |
36.0a1 (2014-10-21), Win 7 x64
STR:
1. Start FF and leave it open
2. Switch theme from Win 7 Aero to Win 7 Basic
3. Click on the Loop button
4. Switch theme back
5. Click on the Loop button
AR: Double edges on the right and bottom sides of the panel. See attached
Comment 1•10 years ago
|
||
Hi Jared, Do you want to try and take this before 11/25 for clean up from bug 1062335?
backlog: --- → Fx36?
Flags: needinfo?(jaws)
Whiteboard: [UX]
Comment 2•10 years ago
|
||
I can't reproduce this issue on Windows 7 64-bit Nightly 10/22/2014.
Flags: needinfo?(jaws)
Reporter | ||
Comment 3•10 years ago
|
||
Try to change the theme couple of more times, and open the Loop panel after every change.
Updated•10 years ago
|
Flags: needinfo?(jaws)
Updated•10 years ago
|
backlog: Fx36? → Fx38?
Comment 4•10 years ago
|
||
This is a general bug with all of our panels after many theme changes. Removing it from tracking with Loop. I don't think this is anything that we should track for Loop, as it has existed for a while and is not something that gets reported often (nor is something that many users will encounter).
backlog: Fx38? → ---
Component: Client → General
Flags: needinfo?(jaws)
Product: Loop → Firefox
QA Contact: anthony.s.hughes
Summary: Visual glitches on theme change → Panel container shows surrounding border after multiple Windows theme changes
Updated•10 years ago
|
Whiteboard: [UX]
Updated•10 years ago
|
Whiteboard: [UX bug]
Updated•2 years ago
|
Severity: normal → S3
Comment 5•5 months ago
|
||
Based on my research Firefox Hello feature was removed in 2016. I have therefore marked it as INACTIVE.
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•