Cool feature, although I note with some irony that once I have the PDF downloaded, I still have to then use Google's Drive PDF reader or some other tool to open it.
Maybe work on a full stack PDF renderer like the desktop version has, Mozilla?
This is in the works. It's the same codebase as the desktop version, which is written in js.
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.
This sounds pretty cool!
I tried enabling it in Fennec (F-Droid "debloated" version with about:config available) and couldn't get it to work. It still downloads PDFs and prompts the system app picker for the viewer.
I don't know what their priorities are but this is the extension I use on firefox mobile so that it can do what safari has been able to do since like ios 3 (open pdf's in the browser). You have to add it to a custom addon collection, which I think you can only enable in beta or nightly: https://addons.mozilla.org/en-US/android/addon/android-pdf-j...
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?
Put simply: PDF content is common enough on the web that it should be viewable as a webpage without having to jump out of the browser app. It breaks the user experience and for searches that may return many pdf results, the minor hassle becomes a major impairment (having to jump between two apps now). It is the case for all desktop browsers for many years now and ios that they open in browser first, so why should it be any different for Android?
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.
Because for a dead simple read-only PDF viewer, I trust Google's security team over random Play Store app to properly sandbox the PDF and not let it do shady shit to my phone upon opening.
I'd trust Firefox more if they provided one, but in their absence, Google has the talent and the resources to do it properly.
Currently, most of the PDF viewers from f-droid report they have a security vulnerability and the f-droid app recommends uninstalling them. For example:
According to the forum discussion [1] you can find the explanations (when they're not included in the app description) in the MaintainerNotes part of the metadata file, which is linked from the page that lists all vulnerable apps [2] and as "Build Metadata" on the page you linked. Not very obvious, but at least the info is available somewhere.
The ones on f-droid are each horrible in its own specific way - some don't support scrolling, some don't support pinch-to-zoom, some have UX from 2012, some don't allow you to save the file (how am I supposed to save a bank statement then?).
No idea why people are complaining about the pdf readers in f-droid.
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).
This is great, though with the usual formatting caveats of pdf printing from any browser! Firefox for Android used to have this feature up to version 60's somewhere but it was removed. I've found it useful on my android to keep an old version of firefox for limited use when I need things like pdf generation or various "unapproved" addons. Now that most of my extensions work on Firefox Nightly (with AMO), and with restored pdf functionality, there isn't much reason to keep the old version around. I'm very happy lately with firefox, both on desktop and android. I wish it would recover some market share from chrome.
Great! It only took them (checks revisions) 2 years to migrate the feature from the old fennec version.
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.
I still miss the tab queue, and the ability to send an URL to another Firefox device from another app, without having to open it in Firefox Android first.
If you go through the rigmarole of setting up an AMO account, installing a pre-release version and then creating a curated list of add-ons and then changing a browser setting, sure!
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!
Would love to have the ability to save webpage (complete) in Firefox again. Currently I'm using SingleFile/SingleFileZ add-ons (and all the hoops you have to jump through to enable those), but they're a lot slower than Chrome mobile which now has the ability to save a page as .mhtml
I have a Samsung printer and have installed the "Samsung Print Service Plugin" on my phone. From Firefox, I can then share the page with that plugin and it prints.
Just tried it, it works pretty well but some elements are rendered in a weird way. It also seems to not save the mobile version of sites you might see on your screen but adjusts the render size to a more paper-like aspect ratio and size. Still, cool feature!
Awesome! This isn't a feature I have a frequent need to use, but it was always disappointing to try to save a page in Firefox for Android and being unable to do so. Now there's one less reason to open Chrome.
I wish there was a browser made exclusively for power users. Something like the Emacs of browsers. I'm tempted to try to make my own like Andreas Kling did.
Is there a similar feature but for taking full page screenshots as well? Using add-ons that do this is unfortunately not allowed on firefox for android.
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.
For those who couldn't be asked to learn how to "Print to File" I assume?
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.
Print TO file, not print a file. Print TO file is to take a screenshot of a page or document to avoid any interpretation issues later.
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.
My workflow has been share->print->pdf for many years. Then view through eboox reader synced over google drive across devices.
I suggest kiwi browser that has kept chrome plugins.
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.
A few years ago I noticed that a few things would get rasterized when going through the print->pdf process and they would stay vectorized (i.e. higher quality) when using the browser's native PDF export feature.
Yeah, and the "new" Firefox mobile engine (Fenix) that is now probably 2 years old never unblocked extensions officially... unless you go the painful collection route.
OT: i really want to use Firefox on Android, except the scrolling performance really sucks and always has, with every device, every FF version, and every Android version. it is so goddamn janky compared to Chrome and Opera (and i assume other Blink-based browsers). i'm on Android 13 and a top-spec Zenfone 9, so it should be a complete non-issue; it's pretty crazy how bad it still is after all this time :(
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.
I always used ff on android and never had any scrolling issue. I can't even understand how could that be. I'm using a Samsung s10e with a very bad exynos cpu.
I've been use Firefox for Android on 12 (and 11 before that) just fine, maybe an Android 13 thing? I can't remember the last time I used Chrome, I used Kiwi & Yandex at some points in the past and didn't notice any significant difference). If you are talking about smoothness, it's possible that I missed it, not caring much, but I've definitely never noticed it being so bad it becomes an usability issue.
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.
I've been using Android Firefox for years. I've rarely seen a scrolling issues. And those were decidedly not on static pages. Mostly the kind choked with ads.
I remember trying to switch to Firefox on Android several years ago and encountering exactly the same issue as you - scrolling was just super janky and unusable.
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).
I'm on a Google Pixel from 2016 and have absolutely no idea what you are talking about. Firefox runs perfectly and I do not see any janky scrolling or otherwise bad performance at all. Scrolling in Chrome does not feel different either.
I wish there was a markup language that gave you the full power relatively of PDF, with page sizes and all of that.
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
HTML and CSS are built for web pages, which means they don't really have a strong concept of page size. If I want to build a table with headers that repeat on every page of a printed document, it's an absolute pain to do it with HTML and CSS.
You need something with constructs that can express pages, repeated tables, headers and footers, stuff like that in a much more native format.
Sorry if I wasn’t clear. I didn’t mean “Make it work with HTML and CSS today”. I meant, Why couldn’t HTML and CSS be used as a basis for a PDF-like format? New features are constantly being added to HTML and CSS. In 5 to 10 years, maybe we’ll have a revamped powerful paged layout that will have all the features that you mentioned.
So my point is, why create a new format when you can enhance HTML and CSS?
Nice feature but what is the use case for saving to PDF? If you want to save a web page for later offline reading then epub would be both much easier to implement and more useful given that it retains ability to reflow to fit different screen sizes. Are there good reasons to prefer a non-reflowable format?
Maybe work on a full stack PDF renderer like the desktop version has, Mozilla?