[macOS] Printing using Save to PDF will not add the .pdf format if the name is changed
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox152 | --- | unaffected |
| firefox153 | --- | affected |
| firefox154 | --- | affected |
People
(Reporter: atrif, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
5.32 MB,
video/quicktime
|
Details |
Found in
- 154.0a1
Affected versions
- 154.0a1 (2026-06-17)
- 153.0b2
Tested platforms
- Affected platforms: macOS 10.15, macOS 12 and macOS 13, 14 (if the file name is changed)
- Unaffected platforms: Windows 11, macOS 26
Steps to reproduce
- Open a page and print it via PDF
- On macOS 13+, change the name of the file (by default, it has .pdf at the end)
Expected result
- The .pdf format is added by default.
Actual result
- The .pdf format is not added.
Regression range
- Pushlog: https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=2a0438e632b2a725d04730193c0740ed576a8675&tochange=4c36e48b14e36f3f453a4a57ca1eeb97b1b905f8
- mozregression points at bug 2038047
Additional notes
- Attached a screen recording.
- Does not reproduce on macOS 26
Comment 1•29 days ago
|
||
:bradwerth, since you are the author of the regressor, bug 2038047, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•29 days ago
|
||
Bug 2038047 doesn't seem a very plausible regressor, IMO. Looking nearby in the pushlog, bug 514491 sounds more likely to be involved here; needinfo-ing Josh as well.
The report says macOS 26 is not affected, but the behavior seems easily reproducible there.
Firefox 152 and 149 behave this way as well. Is this really a regression? Or maybe I'm misunderstanding something?
Chrome behaves the way that this bug suggests is incorrect - the same way Firefox does. It does not add the extension if you delete the extension from the file name in the save dialog.
Safari adds the .pdf extension in this situation, differing from Chrome and Firefox.
| Reporter | ||
Comment 6•29 days ago
•
|
||
Attaching a screen recording from macOS 13: link. In Firefox 152.0.1, no .pdf file extension is shown when using Print → Save to PDF. In Firefox 153.0b1, the .pdf file extension is shown, and if it is removed when renaming the file, the file is saved without the .pdf extension. The regression range was made on macOS 13 based on the .pdf file extension showing and not showing. Note that on 152 the .pdf file exstension is not displayed but the file is still saved as a PDF.
Also attaching a screen recording from macOS 10.15 with 153.0b2 and 152.0.1: here. On macOS 10.15 with 153.0b2, the default filename does not include the .pdf extension, and the file is not saved as a PDF. With Firefox 152.0.1, it is saved as a PDF.
| Reporter | ||
Updated•29 days ago
|
This seems like a desirable change, even if accidental: we should honor what the user has typed into the filename field and we could argue that previously, adding the filename extension was a bug. Our behavior now matches Chrome rather than Safari in this particular case.
Please comment if there is a reason to reconsider this that I may have missed.
Description
•