Closed Bug 1824016 Opened 2 years ago Closed 1 year ago

Feature Callout in PDF viewer does not point to the correct elements in full screen mode

Categories

(Firefox :: Messaging System, defect, P2)

Firefox 111
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: mviar, Assigned: jprickett)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached image Example

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

Change the "browser.pdfjs.feature-tour" pref to '{"screen":"FEATURE_CALLOUT_1_A","complete":false}', opened a PDF in Firefox 111, went to full screen mode (this also occurs if you start in full screen mode)

Actual results:

The feature callout does point to the correct icons in the PDF viewer

Expected results:

It should point to the correct icons in the PDF viewer toolbar in full screen mode.

Component: Untriaged → Messaging System
Assignee: nobody → jprickett
Iteration: --- → 113.2 - Mar 27 - Apr 7
Priority: -- → P1
Severity: -- → S3
Priority: P1 → P2
Iteration: 113.2 - Mar 27 - Apr 7 → 114.1 - Apr 10 - Apr 21

The callout is anchored to the window rather than the browser, so this seems like a difficult problem to solve. I wonder if finding a way to put the pdfjs callout into the content would be a better investment, since it's more generalizable to other use cases, and could also solve the issue of some of our special message actions not working for feature callouts because they pass the doc instead of the browser. That's a complicated refactor but it should basically us up to display callouts in any content window as well as in the chrome (for parent elements that actually exist in the chrome).

Iteration: 114.1 - Apr 10 - Apr 21 → 114.2 - Apr 24 - May 5
Iteration: 114.2 - Apr 24 - May 5 → 115.1 - May 8 - May 19
Iteration: 115.1 - May 8 - May 19 → 115.2 - May 22 - June 2
Iteration: 115.2 - May 22 - June 2 → 116.1 - June 5 - June 16
Iteration: 116.1 - June 5 - June 16 → 116.2 - June 19 - June 30
Iteration: 116.2 - June 19 - June 30 → 117.1 - July 3 - July 14
Iteration: 117.1 - July 3 - July 14 → 117.2 - July 17 - July 28
Iteration: 117.2 - July 17 - July 28 → 118.1 - July 31 - Aug 11
Iteration: 118.1 - July 31 - Aug 11 → 118.2 - Aug 14 - Aug 25

I cannot reproduce this problem with latest Nightly 118.0a1 or with Firefox 111, using macOS 11 and macOS 10.15. The Feature Callout in PDF viewer is pointing the correct icon while being in fullscreen.

Hi, Meg Viar! Are you still seeing this issue with latest Nightly, can you please check again?

Flags: needinfo?(viar)
Attached image screenshot

I can reproduce it on m-c. The window needs to be in fullscreen mode (not DOM fullscreen, i.e. the fullscreen triggered by clicking the fullscreen button on a video, but the one triggered by F11) with a non-native toolbar. Maybe on macOS it requires browser.tabs.inTitlebar to be set to 1 or something. Anyway, in fullscreen mode the toolbar disappears when not hovering or focusing it. But in the process of opening a PDF you might be hovering the toolbar, e.g. drag and dropping a PDF file into the tab strip. And then a PDF tab opens while the toolbar is visible, causing a callout to be positioned under the toolbar. But when you move your mouse out of the toolbar, the toolbar disappears again, leaving a bunch of space above the callout, and the callout does not reposition. Because there's no logic for making it reposition when the coordinates of the anchor element change.

This can technically be fixed by bug 1842366. Loading callouts as panels allows them to 'passively' follow the anchor around the screen. We didn't have express plans to change the existing PDF.js messages, since they aren't shown to any audience now, but when we do the next PDF.js experiment we'll probably implement it that way.

Iteration: 118.2 - Aug 14 - Aug 25 → 119.1 - Aug 28 - Sept 8
Iteration: 119.1 - Aug 28 - Sept 8 → 119.2 - Sept 11 - Sept 22
Iteration: 119.2 - Sept 11 - Sept 22 → ---

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Closing the bug as incomplete.

For more information, please visit BugBot documentation.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Flags: needinfo?(viar)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: