Closed Bug 1819429 Opened 2 years ago Closed 2 years ago

multipage PDF scroll collides with pull to refresh feature

Categories

(Fenix :: Browser Engine, defect)

Firefox 111
All
Android
defect

Tracking

(firefox111 affected, firefox112 affected)

RESOLVED WORKSFORME
Tracking Status
firefox111 --- affected
firefox112 --- affected

People

(Reporter: tif, Unassigned)

References

Details

Steps to reproduce

  1. Find a multi-page PDF on a website e.g. https://static1.squarespace.com/static/573664403c44d8a1804c0ced/t/62324fca82830b19e5cf86f0/1647464394990/bgb+main+menu+-+EDIT+3.16.22.pdf

  2. Scroll to 2nd page, try to scroll back up to 1st page

Expected behavior

I can scroll back to the 1st page without having to reload the PDF.

Actual behavior

As I try to scroll back to the 1st page, I invoke the pull to refresh feature which reloads the whole page. I can't seem to scroll back to the 1st page without reloading the whole pdf.

Device information

  • Firefox version:
  • Android device model:
  • Android OS version:

Any additional information?

From a UX pov, this hinders the ability to easily read and scroll through a pdf. Reloading uses data and perhaps more importantly it causes the user to have to wait in order to peruse their pdf (wait time depends on connection and file size). I believe this needs to be addressed before riding the train to release. At least either PDF or pull to refresh should be held back as that is what is conflicting.

Blocks: 1807071, 1803753
Severity: -- → S3
Component: General → Browser Engine

An easy solution would be to disable pull to refresh when viewing a PDF (it doesn't make sense to reload a PDF anyway).

See Also: → 1809166

I can't reproduce this in nightly 113.0a1 (Build #2015940259). I can't trigger pull to refresh on this pdf. Did we do something to fix this?

(In reply to Marco Castelluccio [:marco] from comment #1)

An easy solution would be to disable pull to refresh when viewing a PDF (it doesn't make sense to reload a PDF anyway).

I think that is also the good solution.

I can't reproduce this either in 111, not sure what fixed it.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.