Closed
Bug 1342948
Opened 8 years ago
Closed 8 months ago
Transform highlighter not always displayed when hovering degree value and it remains stuck when displayed
Categories
(DevTools :: Inspector: Rules, defect, P3)
DevTools
Inspector: Rules
Tracking
(firefox51 wontfix, firefox52 wontfix, firefox53 wontfix, firefox54 fix-optional)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox51 | --- | wontfix |
firefox52 | --- | wontfix |
firefox53 | --- | wontfix |
firefox54 | --- | fix-optional |
People
(Reporter: bmaris, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
1.50 MB,
image/gif
|
Details |
[Affected versions]:
- Firefox 51.0.1
- Firefox 52 beta 9
- latest Aurora 53.0a2
- latest Nightly 54.0a1
[Affected platforms]:
- Mac OS X 10.11
- Windows 10 x64
- Ubuntu 16.04 x32
[Steps to reproduce]:
1. Visit demopage https://bug1312103.bmoattachments.org/attachment.cgi?id=8837541
2. Right click on the icosahedron (geometrical figure with 20 faces) and select inspect element
3. From the Rules panel, hover over 'transform' value.
[Expected result]:
- overlay that shows the original element without transformation is visible on the page no matter where the cursor position is on the transform value.
[Actual result]:
- overlay is not always shown if mouse cursor is positioned on (x deg) values.
- when the overlay is displayed, it's stuck on the page. (moving the cursor on other elements inside Inspector will make it go away)
[Regression range]:
- This is not a recent regression, it's a regression from 2016-05-09:
m-c:
Last good revision: fd8bdef8ef752875c509141b3345ab9e722d6cec
First bad revision: 748b70bcdbc95a4f3e72ca53a23c8f766049d011
Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=fd8bdef8ef752875c5
09141b3345ab9e722d6cec&tochange=748b70bcdbc95a4f3e72ca53a23c8f766049d011
m-i:
Last good revision: 3740695ca00976b5ce2e21424adab26cf19954d8
First bad revision: 730147bfebe3d2c7d3fe1d0848189a8cb0cc8927
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3740695ca00976b5ce2e21424adab26cf19954d8&tochange=730147bfebe3d2c7d3fe1d0848189a8cb0cc8927
[Additional notes]:
- Attached is a screencast showing the issue.
Comment 1•8 years ago
|
||
Too late for 51 and we've built 52 RC. Mark 51 won't fix.
Comment 2•8 years ago
|
||
Sounds like an issue of devtools, but I have no idea why adding new color syntax could break that.
Component: CSS Parsing and Computation → Developer Tools: CSS Rules Inspector
Product: Core → Firefox
Comment 4•8 years ago
|
||
Mass wontfix for bugs affecting firefox 52.
Comment 5•8 years ago
|
||
Dropping this from regression triage since the dev tools team is aware of the issue and has set a priority.
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•3 years ago
|
Severity: normal → S3
status-firefox55:
fix-optional → ---
Comment 6•8 months ago
|
||
This issue is not reproducible anymore using the latest Firefox 132.0 build on Win 10, Ubuntu 22 and macOS 14 ARM. I'm closing it as WFM.
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•