Track Changes - Changes in rules with duplicate selectors are not shown
Categories
(DevTools :: Inspector, defect, P2)
Tracking
(firefox65 verified, firefox66 verified)
People
(Reporter: rcaliman, Assigned: rcaliman)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 2•6 years ago
|
||
Comment 4•6 years ago
|
||
bugherder |
Assignee | ||
Comment 5•6 years ago
|
||
Comment on attachment 9035367 [details]
Bug 1510790 - Introduce Redux selector for tracked changes to return the nested tree structure; r=pbro
[Beta/Release Uplift Approval Request]
Feature/Bug causing the regression: None
User impact if declined: Changes made in different CSS rules with the same selector won't all be shown in the Changes panel. This may constitute data loss if developers rely on the Changes panel for exporting changes. While initially thought to be an edge case, QA found multiple examples where this is an issue on popular websites such as YouTube.
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: None
Risk to taking this patch: Low
Why is the change risky/not risky? (and alternatives if risky): The information about tracked CSS changes was already collected. The issue was correctly rendering this information, which this patch addresses.
String changes made/needed: none
Updated•6 years ago
|
Comment 6•6 years ago
|
||
Comment on attachment 9035367 [details]
Bug 1510790 - Introduce Redux selector for tracked changes to return the nested tree structure; r=pbro
[Triage Comment]
Not crazy about taking this in the last week of the Beta cycle, but the potential dataloss issues sound concerning. Thanks for including automated tests for this at least. Approved for 65.0b11. I would like QA to do some additional testing and verification around this if possible, too, however.
Comment 7•6 years ago
|
||
bugherder uplift |
I managed to reproduce the issue on older 66.0a1 Nightly build (20190102094850) and on the last available 65.0b10 DevEdition build (20190110221328).
I was not able to reproduce the issue on Mac OS 10.13.6.
Verified as fixed using the latest available 66.0a1 Nightly build - 20190114104248 on Windows 10, Windows 7 and Ubuntu 18.04.
Will reverify the fix on DevEdition once a new build is available.
Assignee | ||
Comment 9•6 years ago
|
||
Thank you both for taking this on to beta and for the testing.
Comment 11•6 years ago
|
||
Verified as fixed using the latest available 65.0b11 DevEdition build - 20190114172331 on Windows 10, Windows 7 and Ubuntu 18.04.
Description
•