Open Bug 1450936 Opened 7 years ago Updated 3 years ago

Point is moving opposite way after center [DevTools Shaping Tool]

Categories

(DevTools :: Inspector, defect, P3)

defect

Tracking

(firefox61 wontfix, firefox62 fix-optional, firefox63 affected)

Tracking Status
firefox61 --- wontfix
firefox62 --- fix-optional
firefox63 --- affected

People

(Reporter: david.olah, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [dt-q])

[Affected versions]: Nightly 61.0a1 [Affected platforms]: Platforms: Windows 10 x 64, Windows 7 x 32, Mac OS X 10.12 and Ubuntu 16.04 x64. [Steps to reproduce]: Only for Circle and Ellipse 1. Go to about:config and set "layout.css.shape-outside.enabled" to true. 2. Go to http://labs.jensimmons.com/2016/examples/shapes-2.html 3. Right click on the image and then click on "Inspect Element". 4. Click on the button displayed next to clip-path to toggle the shape tool on 5. Drag a point from the circle/ellipse and drag it through the center [Expected result]: - The point stops in the middle [Actual result]: - The point goes left when dragged right/up when dragged down
Can you please check this issue?
Flags: needinfo?(rcaliman)
The mouse movement isn't clamped for radius editing. This freedom exists with transforms mode too (open editor with ctrl+click / cmd+click). It may not be technically feasible or a good user experience to stop the handle at the middle. This would make it difficult to change again once the user releases the point (in which direction do we clamp if both radius is already 0?). It's more likely that a fix is maintaining the UI consistent update the radius handle to follow the mouse beyond the circle instead of moving in the opposite direction (like it happens on transforms). I'll attempt a fix for this for 62.
Flags: needinfo?(rcaliman)
Assignee: nobody → rcaliman
Status: NEW → ASSIGNED
Priority: -- → P3
Product: Firefox → DevTools
Whiteboard: [dt-q]
Martin from your comment in Trello are you giving this a higher priority? Is it still something you are hoping to fix in 62? It's very late in the beta cycle. Is it a blocker for the feature or can it wait for a fix in 63?
Flags: needinfo?(mbalfanz)
The bug is not a blocker and the feature can continue without it. It's annoying behavior and it would be great to fix it, but it won't cause any crashes or data loss. I'm giving this a higher priority to make sure it lands in 63. If we can't uplift it anymore, then that's totally fine.
Flags: needinfo?(mbalfanz)
Assignee: rcaliman → nobody
Status: ASSIGNED → NEW
Severity: trivial → S4
You need to log in before you can comment on or make changes to this bug.