1565160 - Responsive design mode triggers touch events in the console when clicking on an element

Status: RESOLVED INVALID

(DevTools :: Responsive Design Mode, defect)

Description

[Alin Ilea, Desktop Test Engineering]

Affected versions:

Nightly 70.0a1 (2019-07-10), Beta 69.0b3, Release 68.0

Affected platforms:

ALL

Prerequisites:

Access FF and enter in about:config.
Type devtools.responsive.metaViewport.enabled and set the value to "true".

Steps:

1. Open FF and access https://jsfiddle.net/qyx5qccm/
2. Bring on the RDM (CTRL+Shift+M) and make sure that the Touch Simulation is enabled.
3. Open the inspector (CTRL+Shift+C) then click on "Pick an element from the page" (1st icon button of inspector) click over the red div element in the test page.
4. Click on the Console tab from the Inspector.
5. Refresh the page and click again in the red div element.

Expected result:

No events should be logged in the Console when an element is selected.

Actual result:

Events are logged in the console every click on the red div after refresh the page.

Note: This issue occurs only with touch simulation enabled and just after refresh the page.

Comment 1

[Alin Ilea, Desktop Test Engineering]

Attachment: RDMtouchevents.png

Comment 2

[Razvan Caliman [:rcaliman]]

I'm not convinced this is a bug. It looks like intended behavior for touch events (i.e.: fire as soon as a touch point is placed on / removed from the target area, the "mousedown" / "mouseup" events of the click gesture in this case).

For context try this out in Google Chrome with "Device Mode" enabled:

• open the jsfiddle's output in its own tab: https://fiddle.jshell.net/qyx5qccm/show/
• open the DevTools and switch to the console
• click on the red element

Touch events get fired and logged on every click.

Doing the same in Firefox, the result is the same behavior, however a page refresh is required in Firefox after switching on RDM -- this is probably a bug and should be logged separately.

Comment 3

[Alin Ilea, Desktop Test Engineering]

Hi, Razvan, and thanks for the response.
Based on comment 2 I will close this issue as Resolved - Invalid and will log a new bug for the issue mentioned at the end of the same comment.

Thanks for collaboration.

Comment 4

[Rares Doghi, Desktop QA]

I have added Bug 1565529.