Open Bug 2044669 Opened 22 days ago Updated 21 days ago

Not working with pdf files from Times UK puzzles pages

Categories

(Toolkit :: Printing, defect)

Firefox 151
defect

Tracking

()

UNCONFIRMED

People

(Reporter: beb25hex12, Unassigned, NeedInfo)

Details

Attachments

(1 file)

37.06 KB, application/vnd.oasis.opendocument.text
Details
Attached file FFbugRep.odt

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

Steps to reproduce:

Opened any crossword from thetimes.com/puzzles and tried to use the "gear wheel" (Puzzle Settings) icon and then the Print icon. Settings page in Firefox set to open PDFs in Acrobat.

Actual results:

Rather than opening the pdf it spawns a new tab in Firefox that simply shows the full ip address. In order to download the file I then have to tap in address bar and press return key. A further step is then required to open the downloaded file in Acrobat.

Expected results:

Prior to version 151, and with the correct Firefox settings as above, I could use the Print function from within the Times puzzle page and it would open Adobe Acrobat with puzzle ready fro printing. ONE CLICK rather than a THREE stage process.

The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Printing: Output
Product: Firefox → Core

This seems more on the Toolkit side of things rather than a Core bug.

(I wasn't able to try reproducing this locally, as The Times puzzles appear to require a subscription.)

FWIW, I think I saw someone discussing a similar case quite recently, maybe on Matrix(?), but can't seem to find it right now.

Component: Printing: Output → Printing
Product: Core → Toolkit

After update to version 151 Firefox also appeared to install OpenWeb extension for opening PDFs. Has this any bearing on the problem? I should have stated that I am using Firefox in both Windows 10 and 11 (signed in to Mozilla) and both exhibit the same effect.

If you think Firefox is behaving differently, could you determine a regression range with mozregression.

Flags: needinfo?(beb25hex12)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: