Closed Bug 1198040 Opened 9 years ago Closed 9 years ago

Shouldn't be able to drag/drop <html>, <body>, <head> elements or comment nodes

Categories

(DevTools :: Inspector, defect, P2)

defect

Tracking

(firefox43 affected)

RESOLVED DUPLICATE of bug 1202179
Tracking Status
firefox43 --- affected

People

(Reporter: bgrins, Unassigned)

References

Details

(Whiteboard: [polish-backlog][difficulty=easy])

Dragging/dropping these elements just causes problems. Especially in the case of the <html> tag, the drag seems to never end (or is at least hard to do). IMO we don't need to provide an easy shortcut for moving these elements around, so we should just disable dragging in these case
Dragging the <html> node won't be possible after bug 1176785 is resolved. So this is a partial duplicate of that bug. As for comment nodes, I agree, no real need to allow dragging them around, but what sort of problems can this cause? About body and head, I don't really see a use case for allowing to drag them either. Bug 1176785 introduces a new method to check if an element should be draggable, so let's wait for it to be resolved first. It'll be easy to add conditions to this methods.
Depends on: 1176785
(In reply to Patrick Brosset [:pbrosset] [:pbro] from comment #1) > As for comment nodes, I agree, no real need to allow dragging them around, > but what sort of problems can this cause? Yeah, it doesn't really cause problems in the same way the other nodes do. Actually I added comments to the bug report because I accidentally started dragging one while I was filing this bug. Maybe the issue instead is that it's too easy to accidentally start dragging.
(In reply to Brian Grinstead [:bgrins] from comment #2) > Maybe the issue instead is that it's too easy to accidentally start dragging. 146% agree, so I filed bug 1202179 with specific scenario as an argument.
Priority: -- → P2
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.