Save web pages as PDF in Firefox for Android
support.mozilla.org
support.mozilla.org
Maybe work on a full stack PDF renderer like the desktop version has, Mozilla?
When I used Android, I was never bothered that PDFs opened in the PDF viewer. I was pretty much fine with it. The PDF viewer (not from Google, an open source app) worked pretty much like iBook with a library function, so it was convenient like this actually. It does not look like something to be fixed with high priority. Looks more like a nice to have to me. Why does it matter that they are shown in the browser?
I see the utility in you having an external app to view your pdf's (especially longform books in pdf would be best opened in a dedicated ebook reader app), but there is no consistent user experience on Android, each vendor has their own bundled apps, and some may not even bundle their own app.
I've tested it on low end Android phones from 2017, it works well, when compared to the native offering, and also on modern high end phones, it also works well of course.
What's missing is mobile specific UX, such as pinch-to-zoom, and UX/UI refinements, so it's nice to use.
It has form support, annotations and other goodies like the desktop version as well, which I find very useful.
about:config in Firefox for Android Nightly,pdfjs.disabled to false to give it a go.
Nice! Will it be exposed system-wide so that I can open PDFs from within any other app in Firefox?
Did you have to enable anything else?
I'd trust Firefox more if they provided one, but in their absence, Google has the talent and the resources to do it properly.
https://f-droid.org/en/packages/com.foobnix.pro.pdf.reader/
No explanation on what the vulnerability is.
[1] https://forum.f-droid.org/t/vulnerability-warnings-in-f-droi...
The MuPDF android versions are great, and KOReader is the best ebook and pdf reader I've ever used.
Maybe other people have other use cases, but the above work really well, and don't have known security vulnerabilities (since another commend complained about that).
Seriously though, I'm happy they are making progress and restoring the missing functionality, even if it takes them time. I still miss the dedicated "view-source" button (the feature is ready, but you need to remember the url and then write it) and the swipe to see history/bookmarks directly, but the version is now stable and most of the bugs from the early days are now fixed.
The home screen and the new tab functionality is still a mess though.
Didn't you know that users are too dumb to be able to select add-ons to install themselves? This way, users are protected from themselves!
Also, having to create an account to use addons is not really acceptable to me.
Does anyone know if it's possible yet?
Any day now, I expect them to drop the pretty JSON rendering as well.
Great work as usual.
(EDIT: nevermind ... was mis-remembering ...)
However, I note that "export to pdf" is grayed out for a file that is already a PDF ... which I don't remember being the case ...
Just… use the existing file.
You receive a non-editable pdf ... you use the textbox and signature tools in Preview.app to mark it up and sign it ... and then you export it as a pdf to send back.
How else would I complete that workflow ? Genuinely interested ...
Preview lets you save any annotations to PDFs and images it supports. It’s literally as easy as pressing Cmd-s. If you really want to save it as a different file, use Preview’s duplicate feature to save it as a new file.
If you want to make the file you’re editing non-editable/flattened, then you can use macOS’s built in print dialog which lets you natively save to PDF. This isn’t a Preview feature per-we, but it is system wide.
This seems to have not been possible before and changed in Big Sur: https://discussions.apple.com/thread/252703055
And Apple’s guide considers Save and Export to PDF to be the same function: https://support.apple.com/guide/preview/annotate-a-pdf-prvw1...
I know this is whataboutism but I wish they would have delivered on anti-(canvas-)fingerprinting instead of PDF print.
https://www.ghacks.net/2022/10/20/firefox-beta-for-android-n...
is that a theoretical issue because I've never had any problem with page rendering in Firefox, it's been a major for a long time.
Chrome on iOS also has save as pdf, have to press share, then print, then the share icon again at the top.
I used to use the markup feature as a workaround.
In fairness, save as PDF is more intuitive, but let's not pretend this is anything other than a UI change for functionality that's always been there. A good one, sure, but nothing more.
To print A file, Android has a generic printer driver and there are more featureful proprietary drivers. I printed a shipping label from my phone over wifi the other day. Very easy to detect and add a printer.
It printed slowly and only printed half the page on the first try, but out of the typical printing experience, that's not too bad.
So, probably save as PDF, then print PDF.
Mozilla has managed to slip to irrelevancy with a series of Nokia like decisions. Have no idea why pdf export on Android is any kind of news in 2023 but I hope it is interpreted as a return to some sort of right direction.
unfortunately it's not a minor UX annoyance that you can get used to or simply ignore; it permeates and taints every interaction.
does anyone else have this experience?
EDIT: opened about:support and everything looks fine (webrender, hw accel, hw compositor). interestingly, scrolling the long about:support page is largely jank-free.
EDIT2: went into settings and disabled address-bar hiding on scroll, which seems to have helped quite a bit for web content.
yes. in 2022 on a top-spec phone and latest OS, scrolling of a static google results page or hacker news thread should not stutter. doesn't seem like an unreasonable ask, imo.
Maybe someone would have to point it out for me to notice....
I've recently tried the switch again (a few weeks ago) and did not encounter the same scrolling issues anymore. Could be any number of things that have changed, though, such as a new phone, Firefox updates, OS updates (Pixel 5, Android 13, Firefox 108.1.0).
And a fairly universal converter to turn that markup language into a document.
Then we could use our pre-existing template systems that we use for all the HTML for PDFs and get rid of all these crazy systems that enterprises used to build all the PDF reports
You need something with constructs that can express pages, repeated tables, headers and footers, stuff like that in a much more native format.
So my point is, why create a new format when you can enhance HTML and CSS?
- Scrolling is slow on multiple sites like raycast.com
- The UI doesn't feel home for me, at least it has dark mode on Android 9 (my phone doesnt get updates)
- Tapping new tab doesn't actually create a new tab, instead asks for a URL
- Searching for World cup matches in google only shows the goal score, I guess it's a google search issue, but in chrome I get detailed scorecards
- Tab list view feels janky, why does it automatically switch to another tab, even though I am not closing the current tab? (this happens sometimes)
I will keep using Firefox because Chrome bad.
Go to settings -> add ons and install "Google search fixer"