Closed Bug 1540311 Opened 6 years ago Closed 1 year ago

Screenshot feature not working with touch screen

Categories

(Firefox :: Screenshots, defect, P3)

66 Branch
Desktop
All
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox-esr60 --- affected
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected

People

(Reporter: egil, Unassigned)

References

Details

(Whiteboard: [screenshots-extension])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

  1. Open any page.
  2. Choose screenshot from the page menu (in the address bar).
  3. Drag finger across the screen.

Actual results:

Nothing happens. There seem to be no reaction from the screenshot overlay.

Expected results:

When I touch and drag my finger diagonally I would expect similar behaviour as click+drag. So I would expect to draw/select a rectangle.

Note I'm using Windows 10 with a touchscreen (convertible laptop).

Confirmed on Microsoft Surface Pro and Lenovo Yoga C630. Component set.
Thank you for your contribution!

I have to mention that the screen can be tap-ed to select certain areas, but the feature is lacking touchscreen interaction.

Status: UNCONFIRMED → NEW
Component: Untriaged → Screenshots
Ever confirmed: true
OS: Unspecified → All
Hardware: Unspecified → Desktop

The priority flag is not set for this bug.
:ianbicking, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(ianb)
Flags: needinfo?(ianb)
Priority: -- → P3
Severity: normal → S3
Whiteboard: [screenshots-extension]

The extension implementation of Screenshots is no longer the default. We switched to browser.component.enabled=true a while back and will remove the extension entirely in/around bug 1879396.

That said, we do have a couple of touch-related bugs in the new implementation. That is being tracked in 1935831 - I'll add to the See also field.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
See Also: → 1935831
You need to log in before you can comment on or make changes to this bug.