11–20 of 331 posts
Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
>Firefox Monitor gets its data breach information from a publicly searchable source, Have I Been Pwned. If you don’t want your email address to show up in this database, visit the opt-out page.
Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
> Firefox no longer loads userChrome.css or userContent.css by default improving start-up performance. Users who wish to customize Firefox by using these files can set the toolkit.legacyUserProfileCustomizations.stylesheets preference to true to restore this ability. How much of a performance improvement does this make?
(I'm paranoid and FUDing because I care: there's some UX low hanging fruit before they could get rid of userChrome.css. For instance, you need userChrome.css to autohide the toolbar in full screen mode on macOS — that's not even a customization, it's a missing feature.)
Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
Also, knowing your password wouldn't be enough to identify it within a breach, assuming that the breached website does the bare minimum to store them safely (as in, uses a salt).
How about reading a thing or two before jumping to conclusions?
> Firefox no longer loads userChrome.css or userContent.css by default improving start-up performance. Users who wish to customize Firefox by using these files can set the toolkit.legacyUserProfileCustomizations.stylesheets preference to true to restore this ability. How much of a performance improvement does this make?
Unfortunately they also changed the css model, so even with the flag on - userChrome.css has become useless (to me)... I guess 66 will not be seeing an upgrade for the time being.
As for the question - should be less than 1ms (depends on the OS/filesystem obviously but still negligible)
Wait, Firefox Monitor? As in "allow us to store your email and password in case your email and password are pwned in some other site"? Does anyone else think this is prone to disaster, eventually?
I've been using the Firefox 69 beta since it came out, and with auto-playing audio and video set to blocked, some sites still somehow manage to auto-start muted videos. Is this a bug I should report, or is there some exception that websites are taking advantage of (like starting the video via an event handler like onscroll)?
macOS user base can now consider FF as a viable browser alternative.