41–50 of 209 posts
Earlier quoted context omitted.
Is this using the browser's own JS engine? Do things like NoScript allow one to turn off PDF JS? On the flip side, are there any examples of PDF JS being actually useful and not a vector for tracking/exploits?
You can't use plugins like NoScript with PDFs on Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1454760
> Print updates: Margin units are now localized. Print in firefox is totally broken. The change to Chromium was the last nail in the coffin for printing. The new web does not care.
??? I print through Firefox all the time with no issues. What exactly were you experiencing?
On more and more pages I encounter issues like the printer only printing out the cookie warning window, or just the left navigation bar, etc. and none of the actual page content that I wanted to print. Or content goes up to the first in-line advertisement and then cuts of there with just blank pages coming out of the printer after that. Or weird pagination issues where there's text on page 1 and text on page 2, but there's a bunch of text missing in between that is otherwise visible fine on the screen.
I'm talking about web pages that don't specifically have a "print" button on them. If it looks like the page is using a fancy layout I typically now just do a screenshot and print the resulting .png.
I just switched from FF to Brave. Despite the unnecessarily built-in adblocking (I prefer blocking on router level + 2nd layer via ublock) and the BAT stuff, it is a good browser. It feels so fast and snappy. I wished FF was as fast. Macbook Air M1
Earlier quoted context omitted.
PDFs are definitely not Turing complete. [0] [0] https://www.cs.odu.edu/~zeil/cs390/latest/Public/turing-comp...
Ah I see I may have been thinking of Postscript. Though I'm not entirely convinced they haven't accidentally added Turing completeness back in at some point. I mean you don't really need all that much to write a basic lisp interpreter.
>The ‘Take a Screenshot’ feature was removed from the Page Actions menu in the url bar. Odd, this is the only place I accessed it from. Not a big deal as it's still on the context menu and also can be added as a tool bar item but I am curious the rationalization behind this change. That seemed like a great place to have it to me.
But I think the whole "page actions" button is too hidden. I think screenshot belongs there, and the issue is that most people don't know without being told that "page actions" is something that even exists.
It's great btw to take screenshot of loooong web pages smoothly.
> PDF forms now support JavaScript embedded in PDF files. Some PDF forms use JavaScript for validation and other interactive features. The amount of complexity that one can put into a PDF is both surprising and a tad frightening.
Is this using the browser's own JS engine? Do things like NoScript allow one to turn off PDF JS? On the flip side, are there any examples of PDF JS being actually useful and not a vector for tracking/exploits?
Collections seemingly reinvent the wheel but limit the number of bookmarks, and force me to swipe left to view them.
I thought FTP support had been removed a long time ago for some reason! I have very fond memories of FTP but I guess its time has come. I probably haven't used it for 10 years at this point.
While we have a automatic deployment pipeline for our own projects, lots of our customers that host externally still use good old FTP.
I don't think FTP is ever going to fully die. It is still a typical way to deploy your files when using a shared web hosting that does not offer SSH.
> Print updates: Margin units are now localized. Print in firefox is totally broken. The change to Chromium was the last nail in the coffin for printing. The new web does not care.
I don’t think that Firefox uses code from Chromium for printing, does it? I believe that the print interface merely resembles that of Chromium.