Jump to content

Search the Community

Showing results for tags 'firefox'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 558 results

  1. How to Enable the Lockwise Password Manager in Mozilla Firefox While Mozilla has just released a new version of Firefox, the company isn’t just focusing on the stable browser, but also trying to plan in advance and introducing new features in the early releases of the browser. Firefox Nightly, which is Mozilla’s testing platform for new ideas, now provides users with access to a new password manager that could at some point become available for everyone as well. Called Lockwise, this password manager is actually based on the LockBox app that was previously available on Android and iOS, and it is part of a broader effort to provide users with advanced password management capabilities and sync features across devices. While Lockwise could be pushed to desktop versions of Firefox with dedicated add-ons that would eventually become part of the browser, it looks like Mozilla is already experimenting with a more advanced implementation that makes the password manager a built-in feature. As reported by TechDows, Firefox Nightly already gives us the chance of testing Lockwise right within the browser without the need for installing a dedicated add-on. However, because we’re still in the early days of Lockwise being integrated into Firefox, the feature needs to be enabled manually from the advanced flags screen. So read on for full instructions on how to do it. First and foremost, you need to make sure that you are running the latest version of Firefox Nightly. This tutorial was tested on Nightly build 69.0a1 (2019-05-20) (64-bit), so you need to be running at least this version. Next, fire up the browser and in the address bar, type the following command: about:config Using the search box at the top of the screen, look for the following flag in Mozilla Firefox Nightly: signon.management.page.enabled In the current version of Firefox Nightly, this flag should be set to false, so click the Toggle button to switch it to true. At this point, the Lockwise password manager should be ready for use, and you only need to restart the browser once more to enable it. If you want to access Lockwise in Firefox Nightly after enabling it, click the address bar and type: about:logins This UI is still in its early days, so it doesn’t come with too many features, albeit it does display all logins stored in Mozilla Firefox, along with website address, usernames, passwords, creation dates, last changed, and last used dates. You can edit and delete any entry. Users are allowed to launch the website of a specific account, copy the username or the password to the clipboard. Every time Firefox saves an account when browsing the web, it is displayed not only in the existing password manager that is integrated into the app, but also in Lockwise and shown in this menu. Most likely, Mozilla will continue improving this implementation in the coming updates, so expect further new features to land soon. Mozilla has also launched a Lockwise extension for Firefox on GitHub, so it’s believed that while the company wants to test all these features separately, as part of this standalone add-on, the company could very well integrate the same functionality in the browser as well. This would obviously make Firefox a fully-featured browser without the need for other downloads, albeit this is something that depends on a series of factors, including the feedback regarding the password manager from early testers. At this point, Mozilla is fully tight-lipped on its plans regarding the password manager, so there’s no ETA as to when it could go live. Sooner or later, however, the company is likely to spill the beans on this project, especially as it needs feedback from users. Source
  2. I have noticed recently that NSANE tabs are very slow to switch between if I have more than 1 NSANE tab open. All other tabs are fine. It is only NSANE tabs that are affected. I am using Firefox 64-bit on Windows 10 64-bit. I have just switched to IPS Default theme, and it seems to be quicker.
  3. How to Try Out Mozilla’s WebRender Ahead of the Public Launch in Firefox 67 The next version of Mozilla Firefox is due this week, and in addition to several new features, it will also introduce something that’s not necessarily visible at first glance. With Firefox 67, Mozilla plans to begin the rollout of WebRender, a feature that the company started working on more than three years ago. A commit spotted in September 2015 indicated that Mozilla was working a new technology supposed to enhance the experience online in a new way. WebRender was meant to push the web to “maximum FPS,” technically helping users get smoother browsing thanks to the processing power that their devices boast. WebRender, as Mozilla itself puts it, is already famous for “being extremely fast,” but at the same time, it’s a technology that can help make the browsing experience smoother. “With WebRender, we want apps to run at a silky smooth 60 frames per second (FPS) or better no matter how big the display is or how much of the page is changing from frame to frame. And it works. Pages that chug along at 15 FPS in Chrome or today’s Firefox run at 60 FPS with WebRender,” Mozilla said. Firefox 67 will thus mark the introduction of WebRender for the first users, and Mozilla says the rollout will happen gradually. Only 5% of the users will receive the new system enabled in Firefox based on a series of conditions that are yet to be revealed. However, it’s believed that users must be running Windows 10 and have NVIDIA graphics boards, albeit this is something that is yet to be confirmed. The rollout will take place in stages, so while only a few users would get the new feature at first, more would receive it as Mozilla conducts more testing and receives more information on the actually performance gains. But at the same time, it’s actually possible to enable WebRender even before Mozilla rolls it out officially for your own installation of Firefox. The steps here work in both the beta version and Nightly builds of Firefox, and they are very likely to cover the stable version of Firefox 67 as well once it launches later this week. First and foremost, there won’t be a dedicated option to enable WebRender in Firefox, so you’ll have to do the whole thing from the advanced flags screen. So what you need to do is to launch the browser and in the address bar to type the following command: about:config In the address bar, you need to search for the following flag: gfx.webrender.all If WebRender isn’t enabled on your device, it should be set to false, so click the Toggle button to switch it to true. Mozilla Firefox then needs to be restarted to save your changes and enable WebRender. Once enabled, WebRender should help make the performance overall smoother in Firefox, and the most visible changes will be on high-end displays with enough graphics power. Mozilla could provide more information on the implementation of WebRender in this new Firefox version later this week when the rollout of the new browser begins. In the meantime, it’s not yet clear who gets it, but the aforementioned steps can be used not only on Windows, but also on Linux. Firefox is currently considered the only worthy alternative to Chromium-powered browsers, including here Google Chrome, Vivaldi, and the new Microsoft Edge. Updates and new technologies like this one certainly help the browser become an even better browser, but it remains to be seen how the feature will be received by users worldwide. Source
  4. Translate Man is an add-on for the Firefox web browser that you may use to translate anything that is displayed on a webpage. While Mozilla has been working on integrating a translation service into the Firefox web browser, nothing has come out of that up until now. Extensions introduced support for Google Chrome's translate functionality in Firefox. One of the first, gTranslator for Firefox, replicated Google Chrome's translate feature but with the difference that users had to take manual action. The extension, as well as others such as Translate This, are no longer available. Mozilla started to work on a translation feature in 2014 and integrated some functionality in Nightly versions of Firefox. Mozilla revived the project in late 2018 after years of inactivity targeting Firefox 63 as the stable release for the translate feature. Firefox 63 came but the feature did not make it. Translate anything in Firefox Translate Man is a translation extension for Firefox that you may use to translate anything on-the-fly. The extension works a bit different to how Chrome's translation feature works, but it uses the Google Translate API for its translations. It supports the translation of individual words, phrases, paragraphs and longer text structures. First thing you may want to do is click on the extension's icon in the Firefox address bar to make sure the desired output language is correct. You may use the extension in different ways afterwards: Double-click on any word to translate it instantly. An option to have it pronounced is available as well. Highlight any text to have it translated. Just use the mouse to select text and you get a translation in an overlay next to the selection. Use the Ctrl-key modifier to translate text. Translate on hover automatically. The option is disabled by default. Enable automatic pronunciation of the selected text. You may enable or disable any of these options individually. If you don't want translations when you highlight words, maybe because it is getting into the way of your copy operations, you can disable that option but keep the Ctrl-key modifier one available to use it whenever you need to translate something. Translations pop up nearly instantly on the screen when you use one of the available methods provided by Translate Man. It works really well and there is little to criticize. An option to blacklist languages might be useful to some users but the extension does not get into the way of the user that much anyway. Closing Words Translate Man is a great browser add-on for the Firefox web browser. Firefox users who use translation services at times may find it useful the most, obviously. Source: Translate anything instantly in Firefox with Translate Man (gHacks - Martin Brinkmann)
  5. Mozilla plans to remove configuration options in upcoming versions of the Firefox web browser that allow users to disable the browser's multi-process architecture. Mozilla introduced the multi-process architecture in the Firefox web browser in 2016. Firefox would use multiple processes to divide loaded sites between them and use different processes for the browser's own functionality. While that increased memory usage, it also meant that Firefox would become more stable in the process and less prone to site crashes taking the entire browser with them. Mozilla's implementation was different to Google's. Chrome uses one process per site, Firefox puts multiples sites in a single process. Firefox's Multi-process architecture received numerous improvements over the years. Mozilla added more processes to it and introduced a sandbox security feature later on that depended on it. Mozilla plans to remove two Firefox preferences from any version of the web browser going forward. The change is planed for Firefox 68. browser.tabs.remote.force-enable -- Enforces the use of multi-process in Firefox if it is not enabled by default, e.g. because of accessibility. browser.tabs.remote.force-disable -- Disables multi-process in the Firefox web browser. You probably wonder about browser.tabs.remote.autostart, the preference that enables or disables the multi-process architecture in Firefox (opposed to enforcing a value like the two other preferences do). Mozilla will restrict the preference to true in home builds. While it is still in Firefox, setting it to false in about:config won't have the desired effect anymore once the change lands. The status of the preference is always true in home builds of Firefox regardless of the user chosen value. In other words: going forward, Firefox users can't disable multi-process anymore in the browser. It is unclear in how many Firefox installations multi-process is disabled. Some users do so to improve memory usage or slowness of the browser. Closing Words Mozilla does not reveal why it wants to remove the preference on Bugzilla, only that disabling multi-process should not be "that easy". Additional information is available in a post on the Mozilla Dev Platform group: The broad aim was to ensure that we stop grandfathering users into a non-e10s configuration which they should not run on a day-to-day basis, given that it receives little to no testing and is less secure. It was mentioned as well that Activity Stream breaks if multi-process is disabled. (via Techdows) I'm not particularly fond of changes that remove user choice from any program including web browsers. Mozilla is probably going to get a lot of flak for the removal even if it affects only a minority of users of the browser. Firefox 68 is the next ESR release of the browser. It is scheduled for a July 9th, 2019 release. Source: Going forward, Multi-process can't be turned off anymore in Firefox (gHacks - Martin Brinkmann)
  6. How to Get Extension Recommendations in Mozilla Firefox Like Google Chrome, Mozilla Firefox has one of the largest collections of browser add-ons out there, and in addition to a plethora of extensions, users can also install themes and plugins to further customize the browser. Leaving aside the extension blunder that broke down browser add-ons in Firefox a few weeks ago, one of the priorities for Mozilla is to provide users with easy access to top-rated extensions, but at the same time, to boost the visibility of others. This is how the Firefox Recommended Extensions program came to be, as the parent company wants to make sure that the best extensions are easy to discover. Firefox already comes with a list of recommended extensions in the add-ons screen, but with the Firefox Recommended Extensions program, the company is hoping to also encourage devs to create better extensions. “This program will foster a curated list of extensions that meet our highest standards of security, utility, and user experience. Recommended extensions will receive enhanced visibility across Mozilla websites and products, including addons.mozilla.org (AMO),” Mozilla said when announcing the program. Technically, extensions will be part of the browser if they are “really good” at what they do, “offer an exception user experience,” are “relevant to a general audience,” and are safe to use. While Mozilla said the rollout of the program would take place in stages by the end of June, it looks like the company has already started experimenting with an early version as part of the Nightly build of Firefox. In other words, you can give a try to the Firefox Recommended Extensions program right now by installing Firefox Nightly on any supported desktop platform. However, the feature isn’t enabled by default, so you have to activate it using the steps below. First of all, make sure you are running the latest Nightly build. The tutorial here was tested on version 68.0a1 (2019-05-14), so any release newer than this should work too. Then, in the browser’s address bar tab the following code to access the advanced flags: about:config Hit “yes” when prompted to advance because you understand the risks of messing with these advanced flags and next use the search box at the top to look for the following flag: extensions.htmlaboutaddons.discover.enabled By default, this flag is set to false, so as per TechDows, you need to switch it to true. Once you do that, the Firefox Recommended Extensions program should be active in your browser, and to check it out, follow this path in the browser: Firefox menu > Add-ons > Recommendations At this point, the UI here isn’t much different from the original implementation of recommended extensions, but there are new elements like ratings, number of downloads, and more straightforward information for each item. “Here’s a selection Firefox recommends for exceptional security, performance, and functionality,” the UI reads. “Some of these recommendations are personalized. They are based on other extensions you’ve installed, profile preferences, and usage statistics.” You can simply install an extension, theme, or plugin by simply clicking the “Add to Firefox” button. The new feature should become available to all users by the end of the next month, so despite being offered in the Nightly build of Firefox, it should be promoted to the stable channel pretty fast. The next stable version of the browser is Firefox 67, and it is due on May 21. Firefox 68, on the other hand, which is the version that is being used to test the new extensions program as part of the Nightly build, is scheduled to launch on July 9. Source
  7. Mozilla Releases Fix for Add-On Bug in Older Firefox Versions Mozilla has released an official fix for an add-on issue in older versions of Firefox browser. An expired certificate wreaked havoc for Firefox users in early May, as it disabled extensions in the browser and blocked them from installing new add-ons. Mozilla rolled out updated versions of Firefox to resolve the issue, including Firefox 66.0.4 and Firefox 66.0.5, promising a separate fix for older versions of the browser as well. This fix is now available as a dedicated add-on called Disabled Add-On Fix for Firefox 52-56, and it can be installed from Mozilla using this page. As the description of the extension reveals, simply installing it resolves the bug by deploying a new security certificate in the browser. “On May 3, 2019, an expired security certificate prevented existing and new add-ons from running or being installed in Firefox. We are very sorry for the inconvenience. This extension will install a new security certificate and re-enable extensions and themes for Firefox versions 52 through 56,” Mozilla says. “If you install this extension and then upgrade to a supported version of Firefox, please uninstall this extension as it may not be compatible with updated versions.”Separate patch for Firefox 57 – 65 also in the worksAs per GHacks, the same extension can be used to resolve the issue in other Firefox-based browsers as well including, for example, Waterfox. At this point, Firefox versions 57 to 65 are yet to receive this add-on fix, but Mozilla previously said a patch for these releases was in the works as well. Mozilla last week said it would remove all telemetry data it collected from Firefox users after requiring them to enter its Studies program to receive an emergency fix. The company revealed its investigation on the add-on blunder was still in the works, with more details to be shared at some point in the future after the analysis comes to a conclusion. Source
  8. Good news for Firefox users who run older versions of the web browser that are not supported anymore officially by Mozilla. Mozilla plans to release updates for these web browsers and also a standalone extension to address the add-on signing issue that caused browser add-ons to fail in all versions of the web browser. Mozilla will release an automatic update that fixes the issue for the Firefox versions 52 through 60. Firefox users who run version 61 to 65 may install a browser extension instead to resolve the issue on their end. Last Friday, Firefox users from around the world noticed that the Firefox browser would deactivate all installed browser add-ons. Firefox would display the notification "One or more installed add-ons cannot be verified and have been disabled" to users of the browser. All browser extensions were deactivated in the browser, and it was impossible to enable them again or download extensions from the Mozilla Add-ons website. Mozilla has yet to publish details on how something like this could happened; from what we know, it was a certificate that expired. Since it expired, it could not be used anymore to verify add-on signatures. Mozilla reacted and released a fix through the Firefox browser's Shield studies system at first. The organization pushed out Firefox 66.0.4 and 66.0.5 to the Stable channel, and updates for other Firefox channels as well to resolve the issue. While that took care of supported Firefox installations, it ignored Firefox installations that were not on the most recent version of the browser. Mozilla updated the blog post that it released on May 4, 2019 several times. Yesterday's update highlights that a fix will be released for older versions of the Firefox web browser that are not supported officially anymore. For users who cannot update to the latest version of Firefox or Firefox ESR, we plan to distribute an update that automatically applies the fix to versions 52 through 60. This fix will also be available as a user-installable extension. For anyone still experiencing issues in versions 61 through 65, we plan to distribute a fix through a user-installable extension. These extensions will not require users to enable Studies, and we’ll provide an update when they are available. (May 8. 19:28 EDT) It is unclear how the update for Firefox 52 to 60 will be released. Do users have to search for the update (and risk being updated to a new version of Firefox), or is there another way to push an update to Firefox installations. Mozilla revealed that it would not use the Shield service for that. The organization promised that information will be provided once the update is available. Mozilla plans to release a browser extension for Firefox 61 to 65 that fixes the issue as well. A link will be provided when it becomes available. Closing Words The decision to release updates for older versions of Firefox should please users who are still on that older version, and it should put the (conspiracy) theory to rest that Mozilla broke the system deliberately to force users to update to the latest version of the browser. Something like this should never have happened; it showed how fragile enforced systems can be and how big of an impact simple things can have. It will be interesting to see how Mozilla plans to make sure that something like this won't happen again in the future. Still, it is a good move by Mozilla to release updates for earlier versions. Whether that is the cause for the one-week release delay for the coming Firefox 67 release is unclear at this point. Source: Mozilla will fix add-on signing issue for older Firefox versions (gHacks - Martin Brinkmann)
  9. YouTube Classic is an extension for Mozilla Firefox and Google Chrome that changes the design and layout of YouTube to the classic version. Firefox users can install the browser extension from the official Mozilla Add-ons store; Chrome users cannot, as Google removed it from the Chrome Web Store. It is necessary to load it as an unpacked extension in Developer Mode as explained on the project's GitHub page. YouTube Classic requests access to youtube.com; that's the only permission request and one that make sense, obviously. YouTube Classic Once installed, you will notice that YouTube's layout and design changed to a classic version. The extension replaces the current layout with a classic layout that differs in some regards significantly from the current version. Firefox users may notice a performance boost after installing the add-on when they visit the YouTube website. Some reviewers noted on Mozilla's Add-ons repository site that YouTube loaded significantly faster for them and that the performance was better as well. Core visual differences between the current YouTube layout and Classic YouTube include: Menu is hidden by YouTube Classic. A Load More button is provided in regular and full screen mode to load additional content. Home and Trending links displayed right at the top for easy switching. Fewer links in the header. More video thumbnails are displayed next to each other. YouTube Classic offers one option that is attached to the extension's icon. A click on the extension icon in the browser's toolbar displays an option to turn it off. Just toggle the mode and reload the webpage to go back to the regular version of YouTube. The extension does not reload the page automatically. The "method" option appears inactive at the time. I tried to change it but the selection menu is not active regardless of selected mode. Closing Words YouTube Classic for Firefox and Chrome may appeal to users who prefer the classic design of YouTube over the current design iteration. Firefox users may find it useful besides that as it may improve the performance of YouTube for them. While designed for Firefox and Chrome, YouTube Classic should work in browsers based on Firefox and Chromium code. Source: Restore YouTube's Classic Look in Firefox and Chrome (gHacks - Martin Brinkmann)
  10. Mozilla to Delete Firefox Telemetry Data Collected After Certificate Blunder Mozilla has issued a public apologyafter the certificate blunder that caused Firefox extensions to be disabled, revealing that it plans to delete all telemetry data that it collected when shipping the initial fix. The company blames “an implementation error in one system” as the reason add-ons were disabled, explaining that while the issue has already been fixed now, “we will be working to refine these systems so similar problems do not occur in the future.” Mozilla goes on to reveal that while it collected usage data as part of the Studies program, which it used to deliver the emergency fix, it now wants to delete it completely from its servers. “In order to respect our users’ potential intentions as much as possible, based on our current set up, we will be deleting all of our source Telemetry and Studies data for our entire user population collected between 2019-05-04T11:00:00Z and 2019-05-11T11:00:00Z,” Mozilla says. Some users joined the Studies program only to get the fix on their devices, and Mozilla says that everyone should check their settings before it’s being re-enabled, “will happen sometime after 2019-05-13T16:00:00Z.”More details to be shared soonTo enable or disable Studies in Firefox, open the browser and go to the following path in the application: Firefox Menu > Options > Privacy & Security > Firefox Data Collection and Use Mozilla says that even though the issue has already been fixed as part of Firefox 66.0.4 and Firefox 66.0.5, the company will continue its investigation and share more details as they are discovered. “We let you down and what happened might have shaken your confidence in us a bit, but we hope that you’ll give us a chance to earn it back,” Mozilla concludes. You can download the latest version of Firefox with the certificate bug fix included from Softpedia using this link. Source
  11. Tor Could Help Power a Super Private Browsing Mode in Firefox Mozilla positions privacy at the core of its Firefox browser, and the company wants to continue investments in this area on the long term. In the report covering the research grants for the first half of the year, Mozilla discusses the privacy and security improvements that it wants to make happen in Firefox. One of the priorities, Mozilla says, is to “integrate more of TOR in Firefox,” as the company wants to enhance privacy with what it calls a Super Private Browsing (SPB) for users. Mozilla already has a program to bring Tor features to Firefox. Called Tor Uplift, this effort helped implement fingerprinting protection in the browser, and as per GHacks, Mozilla could further enhance it for the creation of the aforementioned SPB mode too. Tor Browser itself also runs on the Firefox ESR version, providing users with privacy options that aren’t available, or at least not yet, in Mozilla’s browser.The challengesBut as Mozilla itself puts it, implementing more of Tor in Firefox browser isn’t necessarily an easy project, and the purpose of the research grant is to help deal with the challenges such an idea could bring. “Enabling a large number of additional users to make use of the Tor network requires solving for inefficiencies currently present in Tor so as to make the protocol optimal to deploy at scale. Academic research is just getting started with regards to investigating alternative protocol architectures and route selection protocols, such as Tor-over-QUIC, employing DTLS, and Walking Onions,” Mozilla says. Needless to say, this is something that Mozilla is only considering in the long-term and not a feature that is currently under development. The research grants offered by the company are specifically supposed to help pursue such ideas, albeit it goes without saying that not every little project comes to fruition. Source
  12. Some Firefox users started to notice that installed browser extensions were all disabled in the web browser suddenly. Extensions would display "could not be verified for use in Firefox and has been disabled" messages in the add-ons manager of the browser. Firefox would display "One or more installed add-ons cannot be verified and have been disabled" at the top as a notification next to that. Affected extensions include LastPass, Ghostery, Download Manager (S3), Dark Mode, Honey, uBlock Origin, Greasemonkey, NoScript, and others. Only options provided were to find a replacement and to remove the extension in question; this left affected users puzzled. Was this some kind of preemptive strike against policy violation extensions? Mozilla did announce that it would enforce policies more strictly. The answer is no. Turns out, the issue is caused by a bug. If you read carefully, you notice that verification is the issue. A new thread on Bugzilla suggests that this has something to do with extension signing. Firefox marked addons due signing as unsupported, but doesn't allow re-downloads from AMO → All extensions disabled due to expiration of intermediate signing cert. All Firefox extensions need to be signed since Firefox 48 and Firefox ESR 52. Firefox will block the installation of extensions with invalid certificates (or none), and that is causing the issue on user systems. Related issues have been reported: some users cannot install extensions from Mozilla's official Add-ons repository. Users get "Download failed. Please check your connection" errors when they attempt to download any extension from the official repository. Solution Nightly, Dev and Android users may be able to disable signing of extensions; some users reported that this resolved the issue temporarily on their end. You need to set the preference xpinstall.signatures.required to false on about:config to disable signing. You could change the system date to the previous day to resolve it temporarily as well, but that can lead to other issues. The issue can only be resolved on Mozilla's end. The organization needs to renew the certificate or create a new one to resolve the issue. I'd expect Mozilla to do that soon as the issue is widespread and affecting lots of Firefox users. Users should not remove affected extensions from their installations; the issue will resolve itself once Mozilla fixes it. Source: Your Firefox extensions are all disabled? That's a bug! (gHacks - Martin Brinkmann) Poster's note: It's affecting my Firefox, most extensions are now disabled. Grrr...
  13. Karlston

    The future of Firefox for Android

    Mozilla is working on a new mobile browser for Android called Fenix. The new browser is available as a development build currently. The current Firefox for Android is also available but Mozilla focuses development resources on the new Fenix browser; that's the main reason why recent Firefox for Android releases look more like extended support releases that fix bugs but don't introduce a whole lot of new features in the browser. While it was clear for some time that Mozilla planed to replace the current Firefox for Android with the new Fenix browser, it was unclear how all of that would happen. Questions that we had no answers for included for how long the legacy Firefox for Android would be supported, when we could expect a first stable release of Fenix, and how Mozilla planed to migrate users from the old mobile browser to the new. Firefox for Android future A recently published support document highlights Mozilla's plans for the current Firefox for Android and also Fenix. Mozilla's main idea is to maintain the legacy version of Firefox for Android until Fenix reaches migration readiness status. Firefox users on Android should be able to use the legacy version until Fenix is ready while Mozilla wants to minimize support costs. To achieve that goal, Firefox for Android will move to the ESR branch after the release of Firefox 68. In other words: there won't be a Firefox 69 for Android that is based on the legacy version as it will use ESR versioning instead. Timeline for legacy Firefox for Android May 14, 2019: release of Firefox 67 for Android July 9, 2019: release of Firefox 68 for Android September 3, 2019: release of Firefox 68.1 for Android (move to ESR channel) October 22, 2019: release of Firefox 68.2 for Android December 10, 2019: release of Firefox 68.3 for Android The legacy version of Firefox for Android won't receive new feature updates anymore when it moves to the ESR channel. The browser won't receive support for new web technologies anymore, nor will it receive any other feature updates. Bug fixes and security updates will be provided. The releases will follow the Firefox desktop release schedule. Mozilla has not specified a support end for the browser. It seems likely that the browser will reach end of support before mid 2020; Support ends when Fenix is ready and users of the legacy version of Firefox for Android can be migrated to the new mobile browser. Mozilla wants to make it clear that the move to ESR won't give the browser the Enterprise attribute. The main reason why the legacy browser is moved to ESR is that it allows Mozilla to maintain it with minimal effort while work on Fenix continues. The ESR version reaches end of life after Fenix is deemed migration ready by Mozilla. Source: The future of Firefox for Android (gHacks - Martin Brinkmann)
  14. How to Fix the YouTube Screen Flickering in Mozilla Firefox While Google Chrome is the leading browser on both desktop and mobile, Mozilla Firefox continues to be the runner-up on PCs across the world. And there’s a good reason for this, as Firefox remains a super-reliable browser that’s pretty much the only alternative to Chromium, in general, and Google Chrome, in particular. One of the issues that I’ve seen people hitting occasionally concerns what can be best described as a screen flickering on YouTube. Everybody uses YouTube these days, either frequently or occasionally, so it goes without saying that the smallest issue breaking down the online video platform is frustrating, to say the least. In the case of Firefox, one of the most common problems is this screen flickering that makes videos on YouTube unwatchable. While it’s pretty difficult to determine the cause of the bug, mostly because it could be different from one device to another, in many cases, it’s the video drivers the ones to blame. And because it often takes too long before new drivers are published to resolve such issues, there’s a simple flag in Firefox that could help you deal with potential screen flickering on YouTube. First and foremost, it’s important to know that doing this doesn’t guarantee that the screen flickering is gone, but it’s one workaround that’s worth trying, that’s for sure. Then, because it involves disabling hardware acceleration, you should revert the changes once your video drivers are updated, at least to check if the issues are fixed. To disable hardware acceleration in Mozilla Firefox, here’s what you need to do. Launch the browser and make sure that you are running the latest version of Firefox – you can check Softpedia’s Firefox page to always be sure that your version isn’t outdated. Then, in the address bar in Firefox, type the following command to access the flags screen: about:config Click yes when prompted because you “understand the risks” of playing with the more advanced configuration settings of Mozilla Firefox, and then in the search box, look for the following flag: layers.acceleration.disabled By default, this option should come enabled (true) in Mozilla Firefox, so toggle it to false to disable it. You’re going to need to reboot Firefox to check for changes on YouTube, so make sure you save your work before doing this. Restart the browser and then head over to YouTube to check if the screen flickering still happens. If it doesn’t, then this is pretty much the workaround, and the only thing you can do right now is to wait for updated drivers from your manufacturer. There are other issues that could cause screen flickering in Firefox, and in some cases, they could be related to the operating system that you’re running. For example, as I explained several months ago, Google Chrome users also experienced screen flickering on YouTube and on other websites due to Windows Slideshow, a built-in Windows 10 feature that somehow interfered with the settings of the browser. Disabling the automatic color selection on Windows 10 was the workaround in that case, so make sure that you check your OS settings when looking for a way to fix the screen flickering. One way to determine if the issue is related to the browser or not is to check if the screen flickering happens in other applications as well. If you’re on Windows 10, you can try loading a YouTube video in Microsoft Edge, which comes pre-installed in the operating system. If the same issue is experienced regardless of the browser, you can try installing an older version of the graphics drivers. Source
  15. Former Mozilla exec: Google has sabotaged Firefox for years Former and current Mozilla engineers are reaching their boiling points. A former high-ranking Mozilla executive has accused Google of intentionally and systematically sabotaging Firefox over the past decade in order to boost Chrome's adoption. He is not the first Firefox team member to come forward and make such accusations in the past eight months; however, his allegations span far beyond current events and accuse Google of carrying out a coordinated plan that involved introducing small bugs on its sites that would only manifest for Firefox users. OOPS AFTER OOPS Johnathan Nightingale, a former General Manager and Vice President of the Firefox group at Mozilla, described these issues as "oopses." "When I started at Mozilla in 2007 there was no Google Chrome, and most folks we spoke with inside [Google] were Firefox fans," Nightingale recollected in a Twitter thread on Saturday. "When Chrome launched things got complicated, but not in the way you might expect. They had a competing product now, but they didn't cut ties, break our search deal - nothing like that. In fact, the story we kept hearing was, 'We're on the same side. We want the same things'," the former Mozilla exec said. "I think our friends inside Google genuinely believed that. At the individual level, their engineers cared about most of the same things we did. Their product and design folks made many decisions very similarly, and we learned from watching each other. "But Google as a whole is very different than individual googlers," Nightingale said. "Google Chrome ads started appearing next to Firefox search terms. Gmail & [Google] Docs started to experience selective performance issues and bugs on Firefox. Demo sites would falsely block Firefox as 'incompatible'," he said. "All of this is stuff you're allowed to do to compete, of course. But we were still a search partner, so we'd say 'hey what gives?' And every time, they'd say, 'oops. That was accidental. We'll fix it in the next push in 2 weeks.' "Over and over. Oops. Another accident. We'll fix it soon. We want the same things. We're on the same team. There were dozens of oopses. Hundreds maybe?" "I'm all for 'don't attribute to malice what can be explained by incompetence' but I don't believe Google is that incompetent. I think they were running out the clock. We lost users during every oops. And we spent effort and frustration every clock tick on that instead of improving our product. We got outfoxed for a while and by the time we started calling it what it was, a lot of damage had been done," Nightingale said. NOT THE FIRST ACCUSATIONS And Nightingale is not the first Firefox team member to come forward and make such accusations. In July 2018, Mozilla Program Manager Chris Peterson accused Google of intentionally slowing down YouTube performance on Firefox. He revealed that both Firefox and Edge were superior when loading YouTube content when compared to Chrome, and in order to counteract this performance issue, Google switched to using a JavaScript library for YouTube that they knew wasn't supported by Firefox. Source
  16. The next stable Firefox version, Firefox 67, will display a profile icon in the main toolbar to make Firefox Account features more accessible and discoverable in the web browser. Firefox can be used without an account and that won't change; Firefox Accounts are needed to enable sync functionality in the browser and that is without doubt the main functionality right now. Mozilla started to use Firefox Accounts for other web services such as Firefox Monitor, Firefox Send, or Lockbox recently, and there is an option to use a "send tabs" feature to send open tabs to another device. Mozilla ran a Shield Study recently to find out how it could improve the discoverability of the Firefox Account feature. The Shield study ran for 28 days; Firefox displayed an account icon in the main toolbar during the study and this resulted in an 8% increase in sign-ins to Firefox Accounts. Users who participated in the study were asked to fill out a survey. 45% of users liked the profile icon (avatar), another 45% were indifferent to it, and 10% disliked it. Mozilla decided to go ahead and implement a profile icon natively in Firefox to improve Firefox Account discoverability and use. Firefox 67: Profile Icon The profile icon is already visible in Firefox and Nightly versions at the time of writing. It will launch with Firefox 67 in the coming month in the Stable channel. Firefox 67 is scheduled for a May 14, 2019 release. The icon is displayed by default, even to users who are not signed in to a Firefox Account at the time. A click on the icon displays several options that depend on your sign-in status. If you are signed in, you get the following options: Send Tab to another device. Show Synced Tabs. View Synced Tabs Sidebar. Connect Another device. Manage Account. Sync Settings. Sync Now. Note that Firefox does not display options to sign-out of the account using the menu. You need to click on "Sync Settings" to get an option to sign-out of the account. The options are self-explanatory for the most part. Selecting "connect another device" displays an option to send "Firefox" to a mobile device to add it to the main Firefox Account. Managing the Profile Icon in Firefox The profile icon is delivered in a non-fixed status. Means: Firefox users may move it or remove it from the browser's toolbar just like many of the other icons; this is a fundamental difference to Chrome's profile icon which users cannot remove or move. Just right-click on the icon and select "Remove from Toolbar" to remove the icon and hide it. Select "customize" instead if you want to move it to another location. Use drag and drop operations to move it to another place in the user interface after the customize selection. Closing Words Signing in to a Firefox Account is useful if you use multiple versions of Firefox on the same device or multiple devices, and want to sync data between them. It can also be useful as a backup of data that is stored in encrypted form in the cloud. Mozilla does the right thing by allowing users to remove it or move it; those who don't use Firefox Account functionality can remove it once and be done with it. Source: Firefox 67 will display a profile icon in the main toolbar by default (gHacks - Martin Brinkmann)
  17. How to change Chrome or Firefox browser’s User Interface language in Windows 10 Most programs, apps or browsers prefer to use English as their default language. However, not all of us are native English speakers. As such, we like to use apps in our language. If you are interested in knowing the method to change the userinterface language of a browser, read this post and follow the instructions given below. Change User Interface language for your browser If your browser of choice is Google Chrome or Mozilla Firefox and you do not know how to change its user interface language, check this guide. It can help you get your browser work in any language you prefer. This post covers the following: Change Chrome browser user interface language Change Firefox browser user interface language 1] Change User Interface language for Chrome browser By default, Google Chrome configures your OS’s locale as its user interface (UI) language. However, you can readily change it. The simplest way to change this setting in Google Chrome for Windows is via browser settings. So, to begin, Launch Google Chrome browser, click on ‘Menu’ (visible as three dots) and select ‘Settings’ from the list of options. Now, scroll down to the bottom of the page to locate ‘Advanced’ link. When found, click the link. After that, click on the ‘Language’ button and choose ‘Add languages’ if the desired language is not listed. Select the language which you would like to add from the list. Finally, check the box marked against ‘Display Chrome in this language’ option and restart your browser to allow the changes to take effect. 2] Change Firefox browser’s User Interface language Unlike Chrome, Firefox supported two options earlier to change the language of the browser’s interface: Unlike Chrome, Firefox supported two options earlier to change the language of the browser’s interface: 1. Download and install language packs 2. Re-install Firefox using the installer of the desired language. Both these options were considered as inferior to how Google Chrome handled similar changes. Why? The browser enabled its users to directly change the interface language without having to install a language pack or the entire browser. Firefox now has changed this as the browser settings itself integrates language switching options. To change the user interface language in Firefox, load about:preferences in the browser’s address bar. As you might be aware, the page allows you to reset Firefox preferences settings, if needed. When the page opens, scroll down to the ‘Language and Appearance’ section. There, you will find the current interface language displayed under language. Also, you will see a ‘Set Alternatives’ button to change this setting. When visible, click on ‘Set Alternatives’ to add additional languages to Firefox. Select ‘Select a language to add’ and then ‘Search for more languages’. Firefox will instantly start retrieving the list of supported languages from Mozilla. Click on ‘select a language to add’ and pick one of the available interface languages to add it as a language in Firefox. (Note: To jump to a letter in the listing, simply enter the first letter of the language’s name). Next, select ‘Add’ to add the language. Your browser shall download the language pack and automatically add it. Also, if a dictionary is available for the same, it too will be downloaded. Repeat the steps mentioned above for other languages that you would like to add. Once the order of languages is determined, the priority in which they should be used will be set. You can change it anytime by simply moving up or down buttons. Primarily, the preferenceintl.locale.requested determines the priority of languages in the Mozilla browser. However, it is only seen or visible if two or more languages are installed in the browser. Lastly, click on the ‘Ok‘ button to allow Firefox to save the changes made. When it is done, Firefox will display a restart notification. Choose ‘apply and restart’ option to restart Firefox and get started with the new interface language. Source
  18. How to Enable the Dark Mode in Mozilla Firefox Settings UI Dark modes are the new big thing in terms of software user interface, and pretty much every developer out there considers adding one to their apps. Large companies like Google and Microsoft made a huge progress in this regard, so Windows 10, for example, comes with its very own dark mode to make the OS overall easier on the eye during the night. Mozilla is one of the companies that are still working on refining the dark theme in their software, and Firefoxis set to improve even more in the upcoming updates. The most recent changes that the company made to the Nightly build shows that Mozilla is currently in the process of implementing a dark visual style for the about: pages, which, in essence, means that Firefox is set to get a dark mode in settings as well. As with everything that’s being developed by Mozilla, the feature is currently part of Firefox Nightly, as all improvements are being tested here before they are released to everyone as part of the stable browser. Firefox Nightly isn’t recommended as a daily driver, but instead can help you figure out where Firefox is going and to help you try out certain new features in advance. If you want to try out the dark settings screen in Firefox, here’s what you need to know. First and foremost, it looks like this feature currently works on Windows 10 exclusively, albeit there’s no doubt that Mozilla would bring it to all supported desktop platforms sooner or later. But on Windows 10, the dark mode comes with a neat implementation. The browser can adapt to your OS visual settings, so when switching to a dark theme in Windows 10, Firefox can enable the same look in settings as well. However, this behavior requires the dark settings interface to be enabled. As mentioned, this option only exists in the Nightly build, so it you need to activate it manually, but in the stable version of Firefox more straightforward options could be offered too. To try out this new interface, you first have to update to the latest Firefox version. The version that I’m running for this tutorial is 68.0a1 (2019-04-14), so anything newer than this should be alright. Launch the browser and head over to the flags screen to configure additional advanced options. To do this, type: about:config Advance to the next step when asked if you understand the risks of changing the settings here and then search for a flag that is called: browser.in-content.dark-mode By default, this flag is set to false, you need to change it to true by clicking the Toggle button. A browser reboot is then required. If the dark mode is enabled on Windows 10, Firefox should then use a dark theme for the settings screen when reloading the browser. On the other hand, if you want to use the Firefox Settings screen without a dark mode in Windows 10, you can do so by adding a new flag called: ui.systemUsesDarkTheme To do this, copy the flag name, paste in the search box in Firefox about:config screen > Add > True. If everything works correctly, after a browser reboot, the dark theme in the settings UI should be enabled regardless of the visual mode that is running on Windows 10. At this point, there are no specifics as to when Mozilla plans to bring this improvement to all users in a stable version of Firefox. The update, however, first needs to make it from the Nightly build of Firefox to all the other channels before hitting the stable ring. Source
  19. Mozilla published a list of requirements that companies need to meet if they want to be included as Trusted Recursive Resolvers for Firefox's upcoming DNS-over-HTTPS feature. DNS-over-HTTPS aims to improve user privacy, security and the reliability of connections by sending and receiving DNS information using HTTPS. Mozilla ran a Shield study in 2018 to test the DNS-over-HTTPS implementation in Firefox Nightly versions. The organization selected Cloudflare as its partner for the study after Cloudflare agreed to Mozilla's requirements to not keep records or sell or transfer data to third-parties. Firefox users may configure DNS-over-HTTPS in the browser. Mozilla plans to make it the default in Firefox going forward; while that is beneficial overall, doing so comes with its own set of issues and concerns. Firefox will use the feature for DNS related activities and not the DNS configured on the computer. Means: local hosts files, resolvers, or custom DNS providers will be ignored. The selection of Cloudflare as the first partner was controversial. Mozilla plans to make DNS-over-HTTPS the default in the Firefox web browser. Firefox users may still disable the feature once Mozilla makes the switch from off to on though. The organization wants to select a number of companies for use as Trusted Recursive Resolvers in the Firefox web browser. To address concerns in regards to privacy, Mozilla created a list of policies that these organizations need to conform to. User data may only be retained for up to 24 hours and that needs to be done "for the purpose of operating the service". Aggregate data may be kept for longer. Personal information, IP addresses, user query patterns, or other data that may identify users may not be retained, sold, or transferred. Data gathered from acting as a resolver may not be combined with other data that "can be used to identify individual users". Rights to user data may not be sold, licensed, sublicensed or granted. Resolver must support DNS Query Name Minimisation (to improve privacy, the resolver does not send the full original QNAME to the upstream name server). The resolver must not "propagate unnecessary information about queries to authoritative name servers". Organizations need a "public privacy notice specifically for the resolver service". Organizations need to publish a transparency report "at least yearly". The company that operates the resolver should not block or filter domains unless required by law. Organizations need to maintain public documentation that lists all domains that are blocked and maintain a log that highlights when domains get added or removed. The resolver needs to provide an "accurate NXDOMAIN response" when a domain cannot be resolved and not alter the response, e.g. redirect a user to alternative content. Mozilla's system will be opt-out means that it is enabled by default for all Firefox users if Mozilla does not change that prior to integration in Firefox Stable. Source: Mozilla still on track to enable DNS-over-HTTPS by default in Firefox (gHacks - Martin Brinkmann)
  20. However much you love your chosen web browser, you have probably enhanced its capabilities through the use of add-ons. Finding decent, reliable add-ons can be tricky, and this is why Mozilla is launching the Recommended Extensions program. This editor-curated program will surface the very best vetted extensions for Firefox, and it is due to roll out in stages later this summer. Mozilla says that any extensions it recommends through the program will be highlighted across its portfolio of websites and products, including addons.mozilla.org (AMO) and on Firefox's Get Add-Ons page. The company is already identifying extensions it likes the look of, and will soon be reaching out to developers. Changes should be seen on AMO around June. When an extension is chosen, it will be badged to make it easier to identify as a recommendation. Mozilla also says that AMO search results and filtering will be weighted higher toward Recommended extensions In a blog post, Mozilla's Scott DeVaney explains how extensions will be selected for inclusion in the program: Editorial staff will select the initial batch of extensions for the Recommended list. In time, we’ll provide ways for people to nominate extensions for inclusion. When evaluating extensions, curators are primarily concerned with the following: Is the extension really good at what it does? All Recommended extensions should not only do what they promise, but be very good at it. For instance, there are many ad blockers out there, but not all ad blockers are equally effective. Does the extension offer an exceptional user experience? Recommended extensions should be delightful to use. Curators look for content that’s intuitive to manage and well-designed. Common areas of concern include the post-install experience (i.e. once the user installs the extension, is it clear how to use it?), settings management, user interface copy, etc. Is the extension relevant to a general audience? The tightly curated nature of Recommended extensions means we will be selective, and will only recommend extensions that are appealing to a general Firefox audience. Is the extension safe? We’re committed to helping protect users against third-party software that may—intentionally or otherwise—compromise user security. Before an extension receives Recommended status, it undergoes a security review by staff reviewers. (Once on the list, each new version of a Recommended extension must also pass a full review.) Participation in the program will require commitment from developers in the form of active development and a willingness to make improvements. More details will emerge in the coming months. Source
  21. After Chrome, Firefox will also support off-screen image lazy loading Built-in support for image lazy loading coming to Firefox. Google already testing feature in Chrome Image: Mozilla Mozilla engineers plan to add support for "lazy loading," a mechanism to defer the loading of images if they are not visible on the user's screen when a website is first loaded. Work on adding this feature in Firefox started last month. Google has already been testing a lazy loading mechanism in Chrome for over a year, since January 2018. HOW LAZY LOADING WORKS Lazy loading has been a part of the web development scene for more than a decade. It was initially created as a concept for JavaScript libraries. Developers figured out that by delaying the loading of non-visible images, they could significantly improve a website's page load time, a crucial search engine optimization (SEO) criteria, and, hence, obtain a better position in Google search results. The concept spread quickly, and by the early 2010s, there were hundreds of libraries and plugins that provided easy ways to implement a lazy loading mechanism on websites, regardless of underlying programming language or content management system (CMS). GOOGLE WANTED TO SUPPORT LAZY LOADING AT THE BROWSER LEVEL The first step to moving lazy loading from the website level to the browser level was taken in January 2018, when Google published a design document outlining how Chrome would support the lazy-loading of images and iframes that are outside a page's visible section. Chrome flags were later implemented, which are currently available in the Chrome stable version, and which users can enable and have websites load faster. With Google's backing, the feature also became attractive to other browsers, whose developers realized the benefits it could bring to improving page load times, if enabled. Over the past year, Safari engineers have, too, expressed interest in supporting lazy loading. With Firefox putting its backing behind the feature as well, this means that all major browser rendering engines will soon support lazy loading -- WebKit (Safari), Blink (all Chromium browsers), and Gecko (Firefox). We excluded EdgeHTML, as Microsoft Edge will soon move to a Chromium codebase. Source
  22. Firefox Now Blocks “Authentication Required” Prompts By Scam Websites After more than a decade, Firefox finally brings peace to the users annoyed with fake “authentication required” prompts. With Firefox 68, Mozilla decides to put an end on the troublesome login prompts by scam websites. Blocking Scam “Authentication Required” Prompts Reportedly Mozilla’s upcoming Firefox 68 will end up the annoying “authentication required” prompts barraged upon users by scam websites. Mozilla allegedly addressed this problem 12 years after its first report. As stated by Johann Hofmann, a Firefox engineer, in the bug report, Firefox 68 will block spammy login prompts by websites. “For compat reasons, we made the patch in bug 377496 to be a “safe” version of the auth dialog abuse protections, which is still somewhat annoying to users that encounter evil websites.” To fix the problem, Mozilla tightened the restrictions in two ways. First, it blocks the login attempts from the top-level frame, including the site’s main domain. Secondly, it limits the permitted number of cancellations to 2 only. Login Prompt Annoyed Users For Quite Long According to a previous bug report, scam websites tend to trouble users by repeated login prompts. This makes the users lose control of the browser, making them unable to switch tabs or close the window. “A page with many embedded images that require authentication causes the ‘Authentication Required’ dialogue to be shown over and over again.” Consequently, this seemed to cause a denial of service state on the target device. “This gives the possibility of it being used as a DOS style attack, where a page loads random ‘authentication required’ in a JavaScript loop, or simply presenting a page with thousands of embedded images.” This problem not only targeted Firefox users but also affected Chrome users. However, Firefox users faced more of such incidents, particularly from the tech support scam websites. Mozilla attempted to fix the bug earlier. But it didn’t successfully fix the problem as it applied block at the sub-resource level. However, Firefox 68 will eventually end up this problem for good as Mozilla has released the patch with the current Nightly release, whereas it will arrive in the stable version coming in July 2019. Recently, Google also patched the old evil cursor bug in Chrome browser – many tech support scammers actively exploited this bug to target Chrome users. Source
  23. Mozilla revealed in mid-2018 that it had plans to improve the handling of different interface languages in the Firefox web browser. Firefox supported two options back then to change the language of the browser's interface: download and install language packs, or re-install Firefox using the installer of the desired language. Both options were inferior to how Google Chrome handled language changes. Chrome users can change the interface language directly in the browser without the need to install a language pack or re-install the entire browser. The release of Firefox 65 improves how Firefox users may change the browser's interface language. Mozilla integrated language switching options directly to the Firefox settings. Firefox and interface languages Firefox users may still download a different language version of the web browser and install it over the current installation to change the language, but they don't have to if they run Firefox Beta or Stable. Firefox Nightly is excluded because strings change frequently in the browser. Load about:preferences in the browser's address bar. Scroll down to the Language and Appearance section. The current interface language is displayed under language. Click on "Set Alternatives" to add additional languages to Firefox. Select "Select a language to add" and then "Search for more languages". Firefox retrieves the list of supported languages from Mozilla. Click on "select a language to add" and pick one of the available interface languages to add it as a language in Firefox. Tip: tap on the first letter of the language's name to jump to the letter in the listing. Select Add to add the language. Firefox downloads the language pack from Mozilla and adds it to the browser. If a dictionary is available, it is also downloaded. Repeat the process for other languages that you may want to add. The order of languages determines the priority in which they will be used. You may use the move up or down buttons to change the order. Click on the ok button once you are done. Firefox displays a restart notification afterward if you changed the main display language. The restart notification is displayed in the old and new interface language. Select "apply and restart" to restart Firefox so that the new interface language is used. The preference intl.locale.requested determines the priority of languages in Firefox. The preference is only available if two more more languages are installed in the browser. Mozilla hopes to improve the process further in future versions of the Firefox web browser. One possibility that is discussed currently is to complete the migration to Fluent; this would enable restartless language switching and support for non-English fallback locales. Firefox falls back to English automatically if a string is missing from a language file. Closing Words The new language changing options in Firefox 65 improve the process significantly. Everything that is needed is included in Firefox or downloaded automatically from that version of the browser on. While the total number of Firefox installations that have their interface language changed is unclear, it does not appear that uncommon of an operation. Source: How to change the Firefox interface language (gHacks - Martin Brinkmann)
  24. Twelve years later: Firefox to add full protection against 'login prompt' spam Firefox to limit the number of "Authentication Required" popups to two per page. Image: jakebe2 Twelve years after it was first notified of the issue, Mozilla has finally shipped a fix this week that will prevent abusive websites --usually tech support scam sites-- from flooding users with non-stop "authentication required" login popups and prevent users from leaving or closing their browsers. The fix has been shipped in Firefox v68, the current Nightly release, and will hit the browser's stable branch sometimes in early July. According to Firefox engineer Johann Hofmann, starting with Firefox 68, web pages won't be allowed to show more than two login prompts. Starting with the third request, Firefox will intervene to suppress the authentication popup. Mozilla previously shipped a fix for this issue, but it was incomplete, as it blocked authentication prompts that originated from subresources, such as iframes. This latest patch completes the fix by blocking all types of authentication required prompts --including those generated by the site's main domain. FIREFOX USERS TARGETED MANY TIMES WITH LOGIN PROMPT SPAM Authentication prompt spam, also called login prompt spam, has been a problem for internet users for the last two decades. Tech support scam sites have used this trick to trigger infinite loops of "Authentication Required" prompts that block users on sites and prevents them from closing tabs or the browser. The issue has been a problem for Chrome users, but even more so for Firefox, with numerous reports being recorded of tech support scam campaigns using this trick to target Firefox users over the past few years [1, 2, 3, 4, 5, 6]. Browser makers are in a constant fight to fix bugs and loopholes exploited by tech support scammer groups. Mozilla's upcoming Firefox fix helps, but it won't stop tech support scammers, who will just find another trick to exploit. For example, in the past, scammers used tricks like triggering thousands of downloads to freeze users' browsers, they'd create JavaScript infinite loops to keep the CPU at 100 percent and block the browser, or they'd use custom cursors to offset the mouse click area and prevent users from closing tabs. Source
  25. Google's most secure login system now works on Firefox and Edge, too Better hardware security key support means our post-password future is one step closer to reality. Yubico's hardware security keys let you log on without a password on sites, apps and devices that support the FIDO2 authentication technology. Stephen Shankland/CNET Google has updated its support for hardware security keys so you no longer need to rely on its Chrome browser to log into websites like Gmail, YouTube and G Suite. Hardware security keys, small devices that connect to devices wirelessly or with USB, offer better logon security than passwords alone or passwords combined with short-lived numeric codes sent to your phone. But until now, Google's support was limited to an earlier standard called U2F that came with a lot of confines. But now Google updated its login with the newer, broader standard of FIDO2 and its incarnation for websites, WebAuthn. The change means people using Mozilla's Firefox and Microsoft's Edge will be able to log into Google websites with hardware security keys -- though for now they'll still need Chrome to enroll in the system. And later, embracing FIDO2 opens the door for Google to move beyond passwords entirely, since FIDO2 enables authentication with a combination of security key and biometric data like faces or fingerprints. That would be a victory for those who want to move beyond today's plague of problems with passwords. U2F, short for Universal Second Factor, is limited to uses that combine the hardware key with a password. Browsers like Firefox, Edge and Apple Safari don't support it. FIDO2, which like U2F was developed by a consortium called the Fast Identity Online Alliance, encompasses U2F and other options, including just the hardware security key alone. Christiaan Brand, product manager for identity and security, announced Google's move to WebAuthn in a tweet Thursday. On Friday, Mark Risher, director of identity platform and account security, added: "FIDO2 rolling now!" Google didn't immediately comment on when people would be able to use other browsers to enable hardware security key login or whether Google plans to move to passwordless authentication. Google in February embraced FIDO2 for its Androidsoftware, a move that lets people use fingerprints to log into apps. Microsoft has embraced passwordless logon with Windows and online services like Outlook, Skype and Xbox Live. Source
  • Create New...