Track Changes - Changes performed in Geometry Editor using contour drag&drop are not tracked

NEW
Unassigned

Status

defect
P2
normal
6 months ago
4 months ago

People

(Reporter: paul.boiciuc, Unassigned)

Tracking

(Blocks 1 bug)

65 Branch
Unspecified
All
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

6 months ago
[Precondition]

Navigate to about:config and enable the Changes feat. ( devtools.inspector.changes.enabled - True) 

[STR]

1. Launch Firefox and navigate to https://www.w3schools.com/css/tryit.asp?filename=trycss_position_relative
2. Enable the Inspector and select the element with the position: relative. 
3. Navigate to the 3rd panel, Layout tab, and scroll all the way to the Box Model section.
4. Select the small icon on the bottom-right side of the diagram.
5. Once the outer contour is enabled, select the white dot on it and change the position of the element.
6. Observe the value changes in Rule View and then navigate to Changes tab. 


[AR]
Changes tab does not record any changes.
This applies to all elements that can have the outer contour enabled (all except position: static)

[ER]
Changes tab records all changes in position, regardless if this is done by editing the values in Geometry Editor/Box Model diagram or from the outer contour of the element.
Reporter

Comment 1

6 months ago
I've added this as a blocker not necessarily because it might be a blocker, but for better visibility inside the meta bug for Trach Changes M1.
Blocks: 1503920
Priority: -- → P2
Blocks: track-changes
No longer blocks: 1503920
Component: Inspector → Inspector: Changes
Summary: [Track Changes] Changes performed in Geometry Editor using contour drag&drop are not tracked → Track Changes: Changes performed in Geometry Editor using contour drag&drop are not tracked
Summary: Track Changes: Changes performed in Geometry Editor using contour drag&drop are not tracked → Track Changes - Changes performed in Geometry Editor using contour drag&drop are not tracked
You need to log in before you can comment on or make changes to this bug.