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 429 results

  1. Firefox 72: dynamic scrollbars based on page color Mozilla plans to adapt the color of the scrollbar in the Firefox web browser to the background color of the visited webpage in Firefox 72. Dark themes are en vogue currently; operating systems, web browsers, and other applications get dark theme options that users may enable to switch from the previously favored light design to a black design. For many, it seems like a personal preference more than anything else, but dark themes offer some advantages over lighter themes including better battery performance on mobile devices. Firefox users may enable a dark theme in the browser on the Menu > Customize page of the web browser; this paints the browser UI in darker colors. Certain websites, e.g. DuckDuckGo or Startpage, support dark themes as well that users may enable. One of the issues that Firefox users experienced with dark themed sites in the browser was that the scrollbar area was not adapted accordingly. The scrollbar used a light design regardless of website or selected Firefox theme; this felt distracting to many users. Some used custom CSS styles to paint scrollbars in a dark color, others endured the light area on websites visited in the Firefox web browser. Starting with Firefox 72, Firefox will adapt the color of the scrollbar based on the background color of the visited page. Users of the browser who prefer a darker theme will notice that the color of the scrollbar area shines in a darker color as well and that page position indicator is darker than before as well. The screenshot above highlights the change. The window on top shows the new scrollbar color scheme on the dark homepage of the search engine DuckDuckGo. Sites that don't use standards when it comes to dark themes or modes may not show the correct scrollbar colors after all; this is the case for Reddit which, according to a comment on the official bug listing on Mozilla's bug tracking site, sets the dark background "on a child element of the scrollable container" so that Firefox cannot detect the dark theme usage. Firefox 72 Stable will be released on January 7, 2020 according to the release schedule. Source: Firefox 72: dynamic scrollbars based on page color (gHacks - Martin Brinkmann)
  2. Firefox 71: new about:config interface lands Mozilla plans to launch the redesigned about:config interface in Firefox 71, the next stable version of the web browser. The internal page about:config provides Firefox users with access to an advanced set of configuration parameters. The regular options, accessible via Firefox Menu > Options, list only a small fraction of available configuration options. Tip: check out the Ghacks user.js project to find out more about many of the advanced parameters. The pre-Firefox 71 about:config interface is based on XUL, a language that Mozilla deprecated some time ago in favor of web standards such as HMTL5 and JavaScript. The new interface is based on JavaScript and HTML, and will be launched in Firefox 71 Stable if the schedule holds. We looked at the first version of the new interface back in January 2019 and noticed back then that some functionality was missing when compared to the classic about:config interface. To name a few: no deep linking, no sorting, no listing of all preferences, no double-click actions, and less items per page than previously. The final version addresses some of the issues but not all. The final version of the interface supports double-click actions and the display of all preferences that are visible (use * in the search field). Users may also discard changes with a tap on the Esc-key. Some issues, including the removal of deep links and sorting, remain, and Mozilla announced previously that it won't fix those. A quick scan of the Ghacks database returned 48 articles with deep links to Firefox preferences. The instructions won't work anymore when the changed interface lands. While users may look at the filter url to search for the preference name manually, it is far from ideal considering that we are just one website that used the deep linking option to point to about:config preferences directly. Mozilla's initial plan was to release the redesigned interface in Firefox 67 but things got delayed along the way. The organization plans to launch the redesigned interface in Firefox 71. The web browser is scheduled for a release on December 3, 2019 according to the release schedule. Closing words Mozilla addressed some of the issues of the redesigned about:config interface and it seems to have concentrated its efforts on the issues that would have affected the most number of users. It is unfortunate that some features won't be supported; sorting was useful as you could use it to list all modified preferences easily on the screen among other things. Source: Firefox 71: new about:config interface lands (gHacks - Martin Brinkmann)
  3. Actively exploited bug in fully updated Firefox is sending users into a tizzy Fraudulent tech-support sites cause Firefox to freeze while displaying scary message. Enlarge Jérôme Segura 104 with 63 posters participating, including story author Scammers are actively exploiting a bug in Firefox that causes the browser to lock up after displaying a message warning the computer is running a pirated version of Windows that has been hacked. The message, which appears without any user interaction upon visiting a site, reads: Please stop and do not close the PC... The registry key of your computer is locked. Why did we block your computer? The Windows registry key is illegal. The Windows desktop is using pirated software. The Window desktop sends viruses over the Internet. This Windows desktop is hacked. We block this computer for your safety. The message then advises the person to call a toll-free number in the next five minutes or face having the computer disabled. Below is a GIF showing the attack flow: Jérôme Segura The attack works on both Windows and Mac versions of the open source browser. The only way to close the window is to force-close the entire browser using either the Windows task manager or the Force Close function in macOS. Even then, Firefox will reopen previously open tabs, resulting in an endless loop. (Update: as a commenter pointed out, restore tabs is turned off by default.) To resolve the problem, users must force-close Firefox and then, immediately upon restarting it, quickly close the tab of the scammer site before it has time to load. Jérôme Segura, head of threat intelligence at security provider Malwarebytes, said the Firefox bug is being exploited by several sites, including d2o1sv4d11x6bc[.]cloudfront[.]net/firefox/index.html. He said the offending code on the site was written specifically to target the browser flaw. Enlarge Jérôme Segura On Monday, Segura reported the bug to the Bugzilla forum. He said he has since received word Mozilla is actively working on a fix. Firefox representatives couldn't immediately provide information on the status of the bug. Firefox is hardly alone in having bugs that cause the browsers to hang indefinitely while displaying a confusing or scary page. Chrome has had its share of similar flaws, which have also been exploited in the wild. Google developers have since fixed both of them. The exploit spotted by Segura is a common subclass of browser lock attacks. This subclass relies on authentication popups. Earlier this year, Mozilla shipped a comprehensive fix for these types of attacks some 12 years after being reported. Chrome and other browsers have also been vulnerable to this variety of attacks. Segura said he's aware of a separate Firefox browser lock bug that remains unfixed two years after it was reported. Although it was actively exploited in the past, Segura said, he hasn't seen any recent attacks targeting the flaw. For many people, it's not clear what to do when a browser becomes unresponsive while displaying a scary or threatening message. The most important thing to do is to remain calm and not make any sudden response. Force quitting the browser can be helpful, but as Segura has found, that fix is far from ideal since the offending site can reload once the browser is restarted. Whatever else people may do, they should never call the phone number displayed. Source: Actively exploited bug in fully updated Firefox is sending users into a tizzy (Ars Technica)
  4. In a move to fight spam and improve the health of the web, Mozilla will hide notification popups -- a feature nobody asked for. In a move to fight spam and improve the health of the web, Firefox will hide those annoying notification popups by default starting next year, with the release of Firefox 72, in January 2020, ZDNet has learned from a Mozilla engineer. The move comes after Mozilla ran an experiment back in April this year to see how users interacted with notifications, and also looked at different ways of blocking notifications from being too intrusive. Usage stats showed that the vast majority (97%) of Firefox users dismissed notifications, or chose to block a website from showing notifications at all. As a result, Mozilla engineers have decided to hide the notification popup that drops down from Firefox's URL bar, starting with Firefox 72. If a website shows a notification, the popup will be hidden by default, and an icon added to the URL bar instead. Firefox will then animate the icon using a wiggle effect to let the user know there's a notification subscription popup available, but the popup won't be displayed until the user clicks the icon. We've recorded a GIF of this new routine, here. Firefox Nightly versions already come with this notification popup blocker active, but the stable Firefox branch is scheduled to get it next January. The Notification API, and how it all went south Notification popups were added to modern browsers in Chrome 22 (September 2012) and Firefox 22 (June 2013), with the addition of the Notifications API. Their initial purpose was to allow websites to display notifications, and alert users of new content, after users closed a website's tab. For example, you subscribed to Slack notifications, have a conversation, and close the Slack browser tab. The Notifications API allowed websites to show a popup when you received a new message, or there was new content available in your (now-closed) Slack tab. News sites, such as ZDNet, also use notifications to alert users when new articles are out. Social networks and instant messaging clients use it to show alerts for trending topics or new messages. The feature has its use cases, and can be extremely useful, but only when used by legitimate organizations. Fraudsters and spammers love notifications But over the past few years, unscrupulous groups have realized that the Notifications API provides an ideal method of pushing spam to users, even after users left the malicious site. Cybercrime groups have been luring users on random sites, and showing notification popups. If users accidentally clicked on the wrong button and subscribed to one of these shady sites, then they'd be pestered with all sorts of nasty popups. Malicious threat actors have been seen using notifications (also known as subscription spam) to push links to shady products, links to malware downloads, or run-of-the-mill pill or Viagra spam [1, 2]. "Notification spam is quite common, especially via certain types of publishers and malvertising in general," Jérôme Segura, malware analyst at Malwarebytes, told ZDNet in an interview today. "Since most browsers can block ad popups or popunders, push notifications have been greatly abused," Segura added. "In fact, I even question the merits of such a 'feature' in the first place or at least some serious oversight in how it could be implemented. "Years ago, people would come to you about annoying ad notifications popping up on their machine, and that was usually due to adware programs [installed locally]. But these days, I would say this has been largely replaced by notification spam, which is very easy to fall for with some basic social engineering," he added. "In comparison to cleaning up an infected machine, it's actually much easier to remove already allowed notifications, but most people just don't know how," Segura said. And browser makers, too, have realized that the feature can be quite annoying, and downright dangerous. In recent years, most browsers have added settings to block websites from showing notifications. However, Mozilla is the first browser vendor to block notification popups by default. "I think Mozilla's decision is good for the health of the web," Segura told ZDNet. You can unsubscribe from receiving notifications from sites via any browser's settings section. Most browsers support a search feature in the settings section. Users can use it to search for the "notifications" options and block or unsubscribe from the shady sites. Source
  5. Firefox users won't be able to sideload extensions starting March 2020, with Firefox 74. Mozilla has announced today plans to discontinue one of the three methods through which extensions can be installed in Firefox. Starting next year, Firefox users won't be able to install extensions by placing an XPI extension file inside a special folder inside a user's Firefox directory. The method, known as sideloading, was initially created to aid developers of desktop apps. In case they wanted to distribute a Firefox extension with their desktop app, the developers could configure the app's installer to drop a Firefox XPI extension file inside the Firefox browser's folder. SIDELOADING REMOVED BECAUSE OF ABUSE This method has been available to Firefox extension developers since the browser's early days. However, today, Mozilla announced plans to discontinue supporting sideloaded extensions, citing security risks. "Sideloaded extensions frequently cause issues for users since they did not explicitly choose to install them and are unable to remove them from the Add-ons Manager," said Caitlin Neiman, Add-ons Community Manager at Mozilla. "This mechanism has also been employed in the past to install malware into Firefox," Neiman said. TWO-PHASE REMOVAL PLAN As a result, Mozilla plans to stop supporting this feature next year in a two-phase plan. The first will take place with the release of Firefox 73 in February 2020. Neiman says Firefox will continue to read sideloaded extensions, but they'll be slowly converted into normal add-ons inside a user's Firefox profile, and made available in the browser's Add-ons section. By March 2020, with the release of Firefox 74, Mozilla plans to completely remove the ability to sideload an extension. By that point, Mozilla hopes that all sideloaded extensions will be moved inside users' Add-ons section. Through the move, Mozilla also hopes to help clean up some Firefox installations where malware authors were secretly sideloading extensions behind users' backs. Since these extensions will now show up in the Add-ons sections, users will be able to remove any extensions they don't need or don't remember installing. TWO METHODS OF LOADING EXTENSIONS REMAIN Further, Mozilla's blog post on the matter today also serves as a notice for extension developers, who will have to update their extensions and make them available through another installation mechanism. There are currently two other ways through which developers can distribute extensions, and through which users can install them. The first and the most widely known is by installing extensions from the official addons.mozilla.org (AMO) portal. Extensions listed here are verified by Mozilla, so most are relatively safe, albeit the security checks aren't 100% sure to catch all malicious code. The second involves using the "Install Add-on From File" option in Firefox's Add-ons section. Users have to manually download a Firefox XPI extension file, visit the Add-ons section, and then use the "Install Add-on From File" option to load the extension in their browser. This option is usually employed for loading extensions that have to handle sensitive corporate data inside enterprise environments, and can't be distributed via the AMO portal. There was also a fourth method of loading extensions inside Firefox, but this was removed in September 2018, with the release of Firefox 62. This involved modifying Windows Registry keys to load custom extensions with Firefox installations. This, too, was abused by malware devs, and Mozilla decided to remove it. Source: Mozilla to stop supporting sideloaded extensions in Firefox (via ZDNet)
  6. A look at Firefox's upcoming Picture-in-Picture mode Mozilla revealed that it was working on a Picture-in-Picture mode for the Firefox web browser back in February. Designed to play videos in a small overlay on the screen, Picture-in-Picture mode allows users of the browser to navigate between tabs and sites without interfering with the playing video using the detached video player. The original plan was to introduce the mode in Firefox 68 but development has been delayed. Current plans aim for a release in the next stable Windows version of the Firefox web browser, Firefox 71. Firefox 71 will be released on December 3, 2019 if the schedule does not change. Linux and Mac versions of Firefox may see a release in Firefox 72 which will be released on January 7, 2020. Note: The Firefox preference media.videocontrols.picture-in-picture.enabled determines whether Picture-in-Picture mode is enabled. Firefox users may enable the feature already in the browser (there may still be bugs). Firefox Picture-in-Picture mode Firefox adds a small blue icon to supported videos that displays "Picture-in-Picture" when hovered over. A click on the icon opens the video in the Picture-in-Picture interface and displays a placeholder on the original site. It reads "This video is playing in Picture-in-Picture mode". A right-click may also display the option to load the video in Picture-in-Picture mode. The Picture-in-Picture overlay can be moved around on the screen independently and also resized. The interface is not entirely independent but you may change tabs and use the browser normally. The only thing that affects the video is the tab it originated on. If you reload it or navigate away, the video is closed automatically. The Picture-in-Picture interface is bare bones. It features a play/pause toggle button and another for restoring the video in its original location in Firefox. The only other option that is provided is to close the Picture-in-Picture interface by activating the close button. Controls, e.g. to change the volume of the video, change the quality or make other changes, are missing. It is possible to use the controls on the video's original site, e.g. to use the slider to jump to a different position or to change the volume. Here is an overview of all Picture-in-Picture preferences in Firefox: media.videocontrols.picture-in-picture.enabled -- The main preference to enable or disable the feature. media.videocontrols.picture-in-picture.video-toggle.always-show -- Determines whether the PIP icon is shown always (Firefox does not show it for certain videos, e.g. those without an audio track or that are too small in size). media.videocontrols.picture-in-picture.video-toggle.enabled -- Whether to show the toggle to enable PIP mode in Firefox. media.videocontrols.picture-in-picture.video-toggle.flyout-enabled -- Animation when activating the mode. media.videocontrols.picture-in-picture.video-toggle.flyout-wait-ms -- Wait time for flyout mode. Closing words The main benefit of using Picture-in-Picture mode is that users may watch the video unhindered while doing something else in the browser. The PIP window is set to be on top which means that it remains visible even if you navigate to another tab. Firefox users who like to watch videos while doing something else in the browser may find the mode useful the most. Some Firefox users may prefer to play videos in a second browser window, especially if the display offers enough room to display two windows on the screen. Source: A look at Firefox's upcoming Picture-in-Picture mode (gHacks - Martin Brinkmann)
  7. Cloudflare releases Privacy Pass 2.0 extension Internet company Cloudflare launched the Privacy Pass extension for Firefox and Chrome back in 2017 to reduce or even eliminate the number of captchas that Internet users are exposed to. Captchas may be displayed on websites as a form of verification to ensure that the visiting user is a human being and not a bot. Cloudflare operates one of the latest networks on the Internet that many sites use for protection against DoS attacks and for various other functions. If you connect to the Tor network or VPN networks regularly, you may have noticed that the number of captchas that you are need to solve to access sites increases significantly over regular Internet connections. One of the main issues is that the regular system does not take into account previously solved captchas. If you visited a site and solved a captcha, you may still be asked to verify another one on another site. Privacy Pass has been created in collaboration with researchers from several universities to bypass captchas without sacrificing privacy in the process. Privacy Pass, in a nutshell, allows clients to provide proof of trust without revealing where and when the trust was provided. The aim of the protocol is then to allow anyone to prove they are trusted by a server, without that server being able to track the user via the trust that was assigned. Basically, what happens is that users get tokens in advance that may be used later on to bypass captures that would otherwise be displayed. A simple visit to a captcha page could fill up tokens to 30 which would then be used automatically when compatible pages are encountered that require additional verification. Cloudflare launched Privacy Pass 2.0 for Firefox and Chrome on October 28, 2019. The new version makes the extension easier to use, integrates a new service provider (non Cloudflare), and improves the technology used by the extension. The, rather technical, post on the Cloudflare blog provides detailed information on the new version. One interesting new feature is the unlocking of the extension for other services. Cloudflare revealed that a new version of the extension will roll out soon that supports the provider hCaptcha. Internet users who solve a captcha provided by the provider will receive tokens if they run Privacy Pass that will be used automatically on other sites that use the provider's captcha solution. Closing Words The new version of the extension won't convince users who distrust Cloudflare to give it a try. Users who run into captchas, especially those by Cloudflare, regularly, may benefit from it as it should reduce the number of captchas that they are exposed to. Source: Cloudflare releases Privacy Pass 2.0 extension (gHacks - Martin Brinkmann)
  8. Search for webpages in your history and bookmarks efficiently with the Memex extension for Firefox and Chrome Memex is an interesting web browser add-on that is designed specifically for powerusers. Before you ask, no it's not a meme generator. It is a Vannevar Bush inspired bookmarking/local search engine of sorts that you can use to quickly find webpages that you visited in the past. The extension is available for Firefox and Chrome. When you install the add-on, it may appear to be requesting a scary amount of permissions. But they are required for Memex to work. The extension has a visual tutorial which explains how it works; the GIFs that it uses are a bit too speedy for my liking. Once you have installed the add-on, click on its icon (the brain) to bring up a menu and get a few options here. The go to dashboard takes you to the main interface of the extension and the main way you make use of its functionality. Memex indexes pages to make search more powerful in the browser. You need to remember that it saves only the content of individual pages; it is not enough to bookmark the homepage of a site, e.g. Ghacks, to get all articles indexed. The add-on comes with a handy import feature to import pages from the browsing history. For now let's go back to the menu. The "Star this page" option is similar to bookmarking but adds the page to Memex's database, and tags are used to identify starred pages quickly. Just select a page and tag it with a relevant word and it will become usable, or should I say searchable by Memex. You can add multiple tags for a page and collections are like folders to improve organization of webpages. Another way to use these options By default, Memex should add a sidebar and it should be visible when you mouse over to the right edge of the screen. There are buttons here that let you open Memex's dashboard, perform a search, star pages, add tags and perform other actions. There is one important feature which is present in the sidebar which is not in the menu: Notes. The name is a bit misleading as it is an annotation tool. Memex allows you to annotate on any web page. To do so, click the notes icon and type something. For e.g. If you're an Amazon page, you could type something like "This could be an interesting gift for Max's birthday." So, you'll remember why you saved the page and why. You can also highlight text content like you would do with a marker. If you have used Microsoft Edge you may be familiar with these options. When you select text on a web-page, a tooltip should appear and you can use it to link to the highlighted text for reference. When you click on it in the dashboard, you will be taken to the page with the highlighted content visible. Memex also supports keyboard shortcuts. Sidebar - r Star Page - c Add tag - t Add to collections - u Let's star a page, tag it and add it to a collection to demonstrate how this all works and how it benefits you. Say, you want to add the Ghacks homepage to the database. You can visit the page and click on the star icon to bookmark it in Memex. Click on the tag button to add a tag, like Windows Software, Linux apps, or technology. The collection button can be used to add the page to a folder like Tech or Blogs. Note: I found the sidebar to be buggy at times, and used the menu options instead. Now, back to the dashboard. To the left you have your collections, which are sort of like folders for your bookmarks. In the center you have the search box. How does the search work? The add-on can search for the keyword in various ways. Basically it can find any page you have bookmarked or tagged or added to a collection. In addition to this, it can also find pages which you annotated or highlighted text on. It supports full-text search of the web history and bookmarks, and supports filters next to that. You can use the filter option to narrow down the search further by Date - Select a date range (say, October 27, 2019 - October 28, 2019) Tags - Remember how we added tags? Use the same keyword here. Domains- narrow down search by URL (example: ghacks.net) Don't have any of these at hand? Memex can still find the page by the text from titles and URLs. Assuming you added a few pages to the database, perform a search using a relevant word and you should be able to find the page instantly. The best part is that the extension is meant to be an "offline-first" one. It is also open source, and has a good privacy policy. The add-on stores the data on your computer, so your data is yours. You can optionally backup your data on your computer, or to the cloud service of your choice from the settings menu. Memex has a pro version that is completely optional. All it does is automatically backup the data every 15 minutes and supports cross-device sync. Source: Search for webpages in your history and bookmarks efficiently with the Memex extension for Firefox and Chrome (gHacks)
  9. How to restore the green lock icon in Firefox's address bar Mozilla's Firefox web browser used to display a green padlock icon in the browser's address bar when secure sites were opened in the browser. Additionally, the browser would display extended information for sites with EV (Extended Validation) certificates. Mozilla launched a change recently in Firefox that changed the green padlock icon to a gray icon and removed the EV certificate information from the browser entirely. The organization revealed plans in August 2019 to change the information that Firefox displays in the address bar in regards to sites using HTTPS and implemented the change in Firefox 70.0 released recently. Firefox users who open a secure site in the browser see a gray padlock icon in the address bar in Firefox 70 and newer versions of the browser. Sites with EV certificates are not highlighted in any way anymore as well. The main idea behind the changes -- Mozilla is not the only browser developer that made it -- is that the majority of Internet sites are using HTTPS on today's Internet and that the number will increase even more in the coming years. HTTPS is the new default and the reasoning is that sites that don't support it should be highlighted instead of sites that support it. One of the issues with the approach is that generations of Internet users have been trained to look for these locks in the address bar to verify that the connection is secure. While that is still possible as the gray padlock icon indicates a secure connection, some may prefer to get the green icon restored instead as it provides a better visual indicator. Making Firefox`s padlock icon green again Firefox comes with built-in configuration options to restore the green padlock icon. Here is what you need to do: Load about:config in the Firefox address bar. Confirm that you will be careful if a warning screen is displayed. Use the search at the top to find security.secure_connection_icon_color_gray. Toggle the preference so that its value is FALSE. The change is applied immediately, a browser restart is not required. You should notice that all sites that use secure connections are displayed with a green padlock icon again in the Firefox address bar. To restore the gray icon, set the value of the preference to TRUE instead. Restoring Extended Validation Certificate information in Firefox Firefox users may enable the display of EV certificate information in Firefox's address bar as well; this is also done using the method described above: Visit the about:config page again. Search for security.identityblock.show_extended_validation this time. Set the preference to TRUE to enable the display of extended validation information in the browser's address bar. The change is applied immediately. If you don't see it right away try to refresh the site in question. You may set the value of the preference to FALSE to restore the default. Display not secure for sites that don't use HTTPS Firefox displays a crossed-out padlock icon in the address bar by default when a site that does not use HTTPS (or uses it incorrectly) is visited. You may add the "not secure" text to the address bar to further highlight the status of the connection. Visit about:config in the Firefox address bar. Search for security.insecure_connection_text.enabled. Set the value of the preference to TRUE to enable "not secure" or FALSE to disable it. Bonus: If you want to apply the change to private browsing connections as well, search for security.insecure_connection_text.pbmode.enabled and set the value accordingly. Source: How to restore the green lock icon in Firefox's address bar (gHacks - Martin Brinkmann)
  10. Good news: new Firefox for Android will support extensions Mozilla is working on a new mobile browser for Android. Firefox Preview, that is the current name of the browser to distinguish it from the soon-to-be-replaced Firefox for Android, was released to Google Play in mid-2019. The browser will replace the current stable version of Firefox for Android eventually; users of that version may have noticed that it was moved to the ESR branch already to free up resources for Firefox Preview development. Several features of Firefox Preview were not set in stone when Mozilla began development of the mobile browser for Android. One of these features, support for browser extensions, was one of those features. The removal of the feature would cut one of the distinguishing features of the web browser as most Android browsers don't support browser extensions. There was also the likelihood that the decision to ignore extensions would have irritated existing users who use extensions in the current version of the browser. Mozilla announced on October 23, 2019 that Firefox Preview will support extensions. The browser, which is based on the new GeckoView engine, will support WebExtensions just like Desktop versions of the Firefox web browser do. We’re happy to confirm that GeckoView is currently building support for extensions through the WebExtensions API. This feature will be available in Firefox Preview, and we are looking forward to offering a great experience for both mobile users and developers. Support for extension APIs won't match the current level of support in the classic version of Firefox for Android. Mozilla plans to focus its efforts on introducing support for APIs that extensions of the recommended extensions program require to function, and here specifically on APIs for extensions that "work well on mobile and cover a variety of utilities and features". Popular browser extensions such as uBlock Origin, NoScript Security Suite, LastPass Password Manager, Enhancer for YouTube, or Firefox Multi-Account Containers are all recommended extensions. Whether all of these will be fully supported when Firefox Preview will be released as a final version remains to be seen. Mozilla expects to introduce official support for extensions in Firefox Preview in the first half of 2020. Android users interested in Firefox Preview may download the recent version from Google Play. The mobile browser can be installed next to Firefox for Android. Closing Words Extensions support is an important feature of Firefox for Android and it is good to see that Mozilla will implement support for -- some -- APIs in the upcoming version of Firefox as well. The initial release will support only some APIs and not all that Firefox for Android or the desktop versions of Firefox support. While that is disappointing as it means that a number of extensions won't work in Firefox Preview, it is certainly better than not supporting extensions at all. It remains to be seen which extensions will be supported ultimately by the new mobile browser. Source: Good news: new Firefox for Android will support extensions (gHacks - Martin Brinkmann)
  11. Firefox 70.0 is the new stable version of the Firefox web browser as of October 22, 2019. Mozilla releases updates for all channels of the Firefox web browser at the same time; this means that besides Firefox 70, Firefox Beta and Dev are upgraded to version 71 and Firefox Nightly is upgraded to version 72. Firefox ESR versions can only be upgraded to Firefox ESR 68.2 as the 60.x branch is no longer supported. Executive Summary The release marks the end of the Firefox 60.x ESR branch. ESR versions need to update to the 68.x branch. Huge page load improvements on all systems (especially Mac OS X). Firefox 70.0 download and update Updates are made available on October 22, 2019. We publish the release overview early usually to provide users with information prior to the release. Once released, you may run a manual check for updates in Firefox by selecting Menu > Help > About Firefox. Firefox opens a new window that runs a check for update and either suggests to download and install it, or does to automatically. The following pages list direct downloads for supported Firefox channels. Firefox Stable download Firefox Beta download Nightly download Firefox ESR download Firefox 70.0 Changes Article Source: https://www.ghacks.net/2019/10/22/firefox-70-0-release-information/ https://hacks.mozilla.org/2019/10/firefox-70-a-bountiful-release-for-all/
  12. Mozilla working on native Firefox translation feature Mozilla is working on integrating a native translation feature in the organization's Firefox web browser that does not rely on cloud services. One of the advantages that the Chrome browser has over Firefox is that it comes with integrated translate functionality. Mozilla did work on translation features in Firefox and integrated several services, including Yandex Translate and Google Translate in Firefox. The functionality is not enabled by default; one of the main reasons for that is that Mozilla would have to pay the companies that operate the translation services for API use. While Firefox users may get an API key from these services to integrate it in the browser, it is not something that is advertised by Mozilla. Firefox users who require translate functionality install browser extensions such as To Google Translate or Translate Man. The native integration of machine translation functionality in Firefox is part of Project Bergamot, a research project funded by the European Union. The project's consortium is a joint venture of the University of Edinburgh, University of Sheffield, Charles University, University of Tartu and Mozilla. A main focus of the project is to improve client-side machine translations in web browsers to improve privacy and make the solution viable for sectors that can't use cloud-based translation services. The focus of the 3-year Bergamot project is addition and improvement of client-side machine translation in a web browser. This shift to client-side translation empowers citizens to preserve their privacy and increases the uptake of language technologies in Europe in sectors that require confidentiality. Mozilla plans to integrate the project into the Firefox web browser to bring native client-side translation functionality to the browser. A development milestone has been reached recently when the team managed to integrate a basic version of the translation engine in the Firefox web browser (not yet publicly available). A demonstration video has been published on YouTube that shows the client-side translation of a German text into English. The translate functionality uses the same interfaces as the already integrated translate services in Firefox. Mozilla Firefox detects the language of the page and suggests to translate it into a different language based on the user's preference. A click on the translate button starts the process that is handled solely on then local machine. Closing words Project Bergamot is an ongoing project at the time but if the joined research team manages to create a solution that runs machine translations natively and does not lag behind in functionality or performance to cloud-based solutions, it would eliminate one of the shortcomings of the Firefox web browser without sacrificing privacy or costing money that Mozilla would have to pay to third-parties for API uses. Source: Mozilla working on native Firefox translation feature (gHacks - Martin Brinkmann)
  13. Germany's cyber-security agency recommends Firefox as most secure browser Germany's BSI tested Firefox, Chrome, IE, and Edge. Firefox was only browser to pass all minimum requirements for mandatory security features. Image: Mozilla Firefox is the only browser that received top marks in a recent audit carried out by Germany's cyber-security agency -- the German Federal Office for Information Security (or the Bundesamt für Sicherheit in der Informationstechnik -- BSI). The BSI tested Mozilla Firefox 68 (ESR), Google Chrome 76, Microsoft Internet Explorer 11, and Microsoft Edge 44. The tests did not include other browsers like Safari, Brave, Opera, or Vivaldi. The audit was carried out using rules detailed in a guideline for "modern secure browsers" that the BSI published last month, in September 2019. The BSI normally uses this guide to advise government agencies and companies from the private sector on what browsers are safe to use. The German cyber-security agency published a first secure browser guideline in 2017, but reviewed and updated the specification over the summer. The BSI updated its guide to account for improved security measures added to modern browsers, such as HSTS, SRI, CSP 2.0, telemetry handling, and improved certificate handling mechanisms. According to the BSI's new guide, to be considered "secure," a modern browser must satisfy these minimum requirements: - Must support TLS - Must have a list of trusted certificates- Must support extended validation (EV) certificates - Must verify loaded certificates against a Certification Revocation List (CRL) or an Online Certificate Status Protocol (OCSP) - The browser must use icons or color highlights to show when communications to a remote server is encrypted or in plaintext- Connections to remote websites running on expired certificates must be allowed only after specific user approval - Must support HTTP Strict Transport Security (HSTS) (RFC 6797) - Must support Same Origin Policy (SOP)- Must support Content Security Policy (CSP) 2.0 - Must support Sub-resource integrity (SRI) - Must support automatic updates- Must support a separate update mechanism for crucial browser components and extensions - Browser updates must be signed and verifiable - Browser's password manager must store passwords in an encrypted form- Access to the browser's built-in password vault must be allowed only after the user has entered a master password - User must be able to delete passwords from the browser's password manager - Users must be able to block or delete cookie files- Users must be able to block or delete autocomplete history - Users must be able to block or delete browsing history - Organization admins must be able to configure or block browsers from sending telemetry/usage data- Browsers must support a mechanism to check for harmful content/URLs - Browsers should let organizations run locally-stored URL blacklists - Must support a settings section where users can enable/disable plugins, extensions, or JavaScript- Browsers must be able to import centrally-created configuration settings, ideal for wide-scale enterprise deployments - Must allow admins to disable cloud-based profile synchronization features - Must run after its initialization with minimal rights in the operating system- Must support sandboxing. All browser components must be isolated from each other and the operating system. Communication between the isolated components may only take place via defined interfaces. Direct access to resources of isolated components must not be possible. - Web pages need to be isolated from each other, ideally in the form of stand-alone processes. Thread-level isolation is also allowed. - Browsers must be coded using programming languages that support stack and heap memory protections- Browser vendor must provide security updates no longer than 21 days after the public disclosure of a security flaw. If the primary browser vendor fails to provide a security update, organizations must move to a new browser. - Browsers must use OS memory protections like Address Space Layout Randomization (ASLR) or Data Execution Prevention (DEP).- Organization administrators must be able to regulate or block the installation of unsanctioned add-ons/extensions. According to the BSI, Firefox is the only browser to support all the above requirements. Areas where other browser failed include: - Lack of support for a master password mechanism (Chrome, IE, Edge) - No built-in update mechanism (IE) - No option to block telemetry collection (Chrome, IE, Edge) - No SOP (Same Origin Policy) support (IE) - No CSP (Content Security Policy) support (IE) - No SRI (Subresource Integrity) support (IE) - No support for browser profiles, different configurations (IE, Edge) - Lack of organizational transparency (Chrome, IE, Edge) Source: Germany's cyber-security agency recommends Firefox as most secure browser
  14. Firefox 69.0.3 fixes download issues Firefox 69.0.3 will be released to the Stable channel later today. The new version of the web browser addresses two issues, a download issue and a Yahoo Mail issue. Mozilla released Firefox 69.0.2 on October 4, 2019 and became aware of an issue affecting downloads for some users shortly thereafter. Users affected by the issue could not download any files using the browser; Firefox would place a 0-byte file in the download folder but would not download the actual file. Mozilla's investigation revealed that the issue was limited to Firefox on Windows 10 devices and there only if parental controls were enabled. Mozilla implemented checks for parental control software as part of the DNS over HTTPS rollout in the United States. The organization disabled the new feature for devices with parental controls to avoid impacting the functionality of the software. Background updates to Firefox 69.0.2 were throttled as a consequence and work on a patch began. Mozilla acknowledged the issue in the Firefox 69.0.2 release notes stating that "File downloads may not work for Windows 10 users with Parental Controls enabled ". Firefox 69.0.3 Firefox 69.0.3 fixes the download issue for affected users. Interested users can check out the official bug on the official bug tracking website to find out more about the issue and the patch. Firefox 69.0.3 addresses another issue. Yahoo users who use the browser to access Yahoo Mail may have received download prompts when they clicked on emails in the Yahoo Mail web interface. Firefox's downloads manager would list the file "as.php" as the downloaded file on affected systems. Fixed download errors for Windows 10 users with Parental Controls enabled (bug 1586228) Fixed Yahoo mail users being prompted to download files when clicking on emails (bug 1582848) Firefox 69.0.3's official release date is October 10, 2019. Firefox users affected by the issue may run a manual check for updates once the browser is released officially to upgrade to the new version immediately. All that needs to be done for that is to click on Menu > Help > About Firefox. Closing words Mozilla fixed both issues in less than a week's time. Affected users may have downgraded Firefox to an older version to mitigate the issue for the time being. Firefox 69.0.3 fixes the issue and users should consider upgrading to the new version. Source: Firefox 69.0.3 fixes download issues (gHacks - Martin Brinkmann)
  15. Link Gopher is a Firefox add-on that can extract links from webpages Most websites have tons of links in their pages. Some of these may be used as internal links to pages within the same website while others are outbound links to other resources. If you want to find out how many links a page has or even extract links from a webpage, it could be a difficult job to handle this manually. There could be hundreds of URLs. The Firefox add-on Link Gopher can do this for you as it was written specifically for extracting links from webpages. The add-on adds an icon to the Firefox toolbar when you install it that displays a light interface that consists of just 3 buttons. Extract all Links Extract all Links by Filters About Link Gopher (links to the official website). Extract all Links Go to any web page and click on the "Extract all Links" option and Link Gopher will open a new tab in Firefox that contains all the links that were found on the web page. All of these links are clickable so you can use them directly from the browser. Internal links and links to other resources are displayed under Links. Scroll down to the end of the page to see "Domains", i.e., links to the top-level domain of other websites. The list of the links follows the browser's colour policy to distinguish visited URLs. You can also save the links to a document manually if required. This can be useful for webmasters or if you're on a web page with several download links. It was handy during my tests as it could pull all the direct download links from web pages and saved me a few extra clicks now and then. Another example when I found the add-on to be particularly helpful was when I used it to find the "source link" in articles on other websites. Many writers and admins make it a practice nowadays to hide outbound links within words used in the article. It is good for SEO but the reader may find it difficult to spot the link, especially if it is of the same colour as the rest of the text. Extract all Links by Filters This option may appear quite similar to the normal extractor, but it's quite different. When you click on this option (from a source web page), you will see a search box that accepts keywords, e.g. If you only want to see links from gHacks, type "ghacks" and click on the ok button. Link Gopher will filter the links from the page, and you will only see the links which have the word "ghacks" in the URLs. Sadly, Link Gopher does not offer any customization whatsoever. I'd have preferred to have an option to open links in a new tab by default, well nothing a control + click (or middle-click) won't do. That being said, the add-on is meant to do one job and it excels at what it does. Link Gopher is open source, but I couldn't find the source of version 2 of the add-on. Mozilla has marked it as a recommended add-on which is a good sign. Source: Link Gopher is a Firefox add-on that can extract links from webpages (gHacks)
  16. Mozilla says in an update to the Firefox 69.0.2 changelog that downloading files from the Internet may not work for Windows 10 users who have the Parental Controls feature toggled on and are part of a family group. The problem is described on Reddit [1, 2, 3] and Mozilla's bug tracker in an issue reported three days ago, on October 4, saying that all web downloads are failing when using Firefox on Windows 10. Don't update to 69.0.2 or 70.0b11+ Following these reports and the bug tracker issue, Mozilla published a support page where it advises Windows 10 users to refrain from updating their Firefox installation to—the web browser's latest stable version released last Thursday—or Beta 70.0b11+ until a fix is available. "There is a known issue in Firefox 69.0.2 and Beta 70.0b11+ that causes downloads to fail in Windows 10 when you have parental controls or content restrictions on," says Mozilla. "If you haven't already updated to 69.0.2, please avoid doing so until we've shipped a fix." While a patched version is not yet available in the Stable or Beta channels, the releases affected by this issue, Mozilla recommends users that, "in the meantime, you can work around this problem by turning off content restrictions [..]." This can be done using a step by step procedure described in this Microsoft support article and designed to remove members from a family group via the family.microsoft.com portal: 1. Go to family.microsoft.com. 2. Sign in with your Microsoft account, then: • To remove a child, scroll down and select Manage my child's profile info, select the child, select Remove consent for this child's account, and confirm. Then, go back to your family’s page, and under the child’s name, select More options > Remove from family, and confirm. • To remove a child because they’re now an adult, or if an adult account has been misclassified as a child account, verify the account. • To remove an adult, under that person's name, select More options > Remove from family, and confirm. • To leave the family group if you’re the only adult in the family, remove all children first, then find your name, select Leave family, and confirm. You must be over the statutory age to remove yourself. • If you're incorrectly listed as a child when you're an adult, see How to change a birthdate on a Microsoft account. Users who have already installed the impacted Firefox versions will have to downgrade to a previous stable version that is not affected by this bug (69.0.1 or 68.0.2 might do the trick according to some user reports). Fix coming in a future release While Mozilla can use hotfixes to patch some browser issues, it seems that this one might have to wait to get fixed as part of future releases in the Firefox stable and beta channels. "A patch to the parental controls service that makes it return that downloads are allowed instead of throwing seems to fix the problem," says Mozilla Platform Engineer Matt Howell. "That would require a new release; I'm not sure what our current hotfix capabilities are, but I would guess that anything we could do to fix this would fall outside of them." Until then, Firefox users with Windows 10 devices can either leave any family groups they're in or downgrade to a previous release not yet affected by this bug. Source
  17. Firefox 69.0.2 is out, here is what is new Mozilla released Firefox 69.0.2 today; the stable channel update fixes two potential crashes in the web browser and fixes the detection of Parental Controls on Windows 10. The update is already available via the web browser's built-in automatic updating functionality. Firefox users should receive update notifications when they run the browser. Users who want to speed up the process -- it may take a bit of time before the browser runs the check for updates -- may run a manual check instead. To do that, select Menu > Help > About Firefox. The browser displays the installed version and runs an update check. The new version is either downloaded and installed automatically or manually depending on the browser's preferences. Firefox 69.0.2 is the second minor update of Firefox 69.0. Mozilla released Firefox 69.0 on September 3, 2019 and pushed out the first minor update, Firefox 69.0.1, on September 18, 2019. Firefox 69.0.2 Firefox 69.0.2 is a bug fix release that addresses two crashes in the browser. Fixed a crash when editing files on Office 365 websites -- The first issue affected Office 365. Mozilla's release notes highlight that the issue could crash the tab when editing files on Office 365 websites. Some reports suggest that the tab could also crash when navigating pages on Office 365 websites. Firefox 69.0.2 fixes the issue, tabs should not crash anymore on Office 365 sites. [see bug 1579858] Fixed a Linux-only crash when changing the playback speed while watching YouTube video -- The second crash affected Firefox on Linux only. Firefox users who changed the playback speed on YouTube while watching videos on Linux could encounter freezes or tab crashes when doing so. [see bug 1582222] Fixed detection of the Windows 10 Parental Controls feature being enabled -- Mozilla fixed the detection of the Parental Controls feature on Windows 10 devices. The issue affected the rollout of the DNS over HTTPS feature in the United States that started in September. Firefox was designed to keep DNS over HTTPS disabled if Parental Controls were used, and the bug affected that logic. [see bug 1584613] Firefox users who are affected by any of the issues may want to upgrade the web browser immediately to resolve the crashes. There is no hurry for users not affected by the issues to install the update as the fixes will be part of the Firefox 70 release on October 22, 2019. Source: Firefox 69.0.2 is out, here is what is new (gHacks - Martin Brinkmann)
  18. FoxyTab is a highly customizable tab manager extension for Firefox There is no shortage of tab managers for Firefox but FoxyTab is one that goes all out for customization. It's a very user-friendly extensions that adds nifty little options that you may find handy to improve your workflow in one way or another. Tip: check out our Firefox Tab Mastery guide for getting the most out of the browser. Once installed, the add-on's icon is placed on the toolbar and will immediately display a badge; it represents the number of tabs that are currently open in the browser. You can optionally disable this or change the badge/text colour from the extension's options. Clicking on the add-on's icon will only let you access the options or recount the tabs. The real interface of FoxyTab is in the tab bar. Or to be more precise, right-click on the tab bar and you will see a new context menu called FoxyTab. These are the options that are available in the context menu. Duplicate Tab Close Duplicate Tabs Close Tabs to the Left Merge all Windows Close Other Windows Save Tab as PDF (Not on macOS or pre-Firefox 56) Create Desktop shortcut Copy Bookmark Host Sort Reload Most of these are self-explanatory so we'll focus on the ones which are special. The Copy option lets you copy the tab title, URL, or tab title and URL. You can also use it to copy all URLs from open tabs or all the Titles, or both. There are even options to copy URLs and Titles from the tabs to the right or the left of the current tab so that every possible use case should be covered by these options (except for selecting individual tabs). These options save you a ton of time and can be used to save an entire session to a text document (very handy if you are a OneTab user). In addition to those, you can also use the Copy IP option to find out the IP address of a website really quickly. You can define your own parameters for the Custom Copy menu using these placeholders: {ip} {title} {url} {date} {time} \n \t Note: You'll need to refresh a tab if you loaded it with the undo closed tab option to find the IP. The Bookmark option lets you save tabs to the Left/Right of the current tab. This can be a great way to save a ton of pages with a single-click of the mouse and it complements Firefox "bookmark all" option nicely. The Host menu is for closing all the tabs, other than the one that is in view, or the one that you right-clicked upon to access FoxyTab. Sort Tabs is one that I found to be a rather niche option. If you want to sort the list of tabs in ascending or descending order of the URL or Title, well you can do that. I did like the move options which can be used to move tabs to the left or right in a new window. It also works with private windows without hitches. The Reload menu has 3 settings: reload all tabs, or just the ones to the left or right, and reload tab every few minutes (can be customized). That could save the F5 key, for e.g. when you are waiting for the end of an auction on eBay or the time an item becomes available online. You can disable or enable any of the context menu items from the add-ons preferences to create a cleaner menu that focuses on the options that you need. Speaking of which, You can import and export the add-ons preferences. I recommend using this one to backup your settings in case you want to refresh Firefox or use different installations or profiles. The Hidden options FoxyTab has a few extra settings that you can choose to enable such as a Clock, Date or Month. You can customize these, and even use multiple clocks with different time zones if you want to. Firefox Multi-Account Container add-on users can configure FoxyTab to open domains in specific containers. Closing Words FoxyTab is a helper extension for Firefox that may improve productivity by extending Firefox's tab-based capabilities. Whether it is an option for you depends on your Internet usage and how you use the Firefox web browser. Source: FoxyTab is a highly customizable tab manager extension for Firefox (gHacks)
  19. Mozilla disables TLS 1.0 and 1.1 in Firefox Nightly in preparation of deprecation Firefox maker Mozilla disabled support for the protocols TLS 1.0 and TLS 1.1 in recent versions of the Firefox Nightly web browser. Major browser makers such as Mozilla and Google announced in 2018 that support for the decade-old standards would be dropped in 2020 to improve the security and performance of Internet connections. Back then it was revealed that TLS 1.1 was used by 0.1% of all Internet connections; the number has likely gone done in the meantime. Transport Layer Security (TLS) is a security protocol used to encrypt Internet traffic; TLS 1.3 Final was published in 2018 and companies started to integrate the final version into browsers shortly thereafter. Mozilla started to enable TLS 1.3 in Firefox Stable in 2018, and other browser makers such as Google added support for the new protocol version as well. Tip: here is a way to determine if your browser supports TLS 1.3 and other security features. Firefox and TLS 1.0 and 1.1 deprecation Mozilla disabled support for TLS 1.0 and TLS 1.1 in Firefox Nightly in preparation for the deprecation in Firefox Stable in 2020. A quick check on a SSL Labs test site confirms that TLS 1.2 and 1.3 are the only supported protocols by the browser. Sites that support TLS 1.0 and/or TLS 1.1 but not TLS 1.2 or newer will fail to load and throw a "secure connection failed" error instead. The error code is SSL_ERROR_UNSUPPORTED_VERSION. Firefox users may override the limitation in the following way currently but that option will likely go away once the change lands in Firefox Stable in early 2020. Load about:config in the web browser's address bar. Confirm that you will be careful. Search for security.tls.version.min. The default value of the preference is set to 3 which means that Firefox accepts TLS 1.2 and higher only. Change the value to 2 to add support for TLS 1.1, or to 1 to add support for TLS 1.0. The screenshot below shows the default value of the preference. Sites, including the dashboard of modems, routers and other local peripheral devices, that support only TLS 1.1 or TLS 1.0 will load after you make the change. Closing Words TLS 1.0 and 1.1 support will be removed from browsers in early 2020. While that should mean minimal interruption for most users, some, especially those working in local Intranets and other non-Internet environments, may run into issues connecting to certain sites and devices that don't support newer protocol versions for one reason or another.Some browsers may keep support for TLS 1.0 and 1.1 enabled, and it is also possible to use an older version of a browser to connect to these sites. Source: Mozilla disables TLS 1.0 and 1.1 in Firefox Nightly in preparation of deprecation (gHacks - Martin Brinkmann)
  20. How to import tabs from Chrome to Firefox and vice versa So, you have decided to switch from Chrome to Firefox, or maybe it's the other way around. The problem is you have a lot of tabs opened, and you can't abandon the session. Or, you use both web browsers regularly and want to push tabs from one browser to the other; this may also be useful for developers who need to test their sites in different browsers. What do you do? Manually copy and paste each URL from one browser to the other? That could take a long while depending on the number of tabs that you want to push to the other browser. The browser extension OneTab offers a solution that improves the process especially if you need to push multiple tabs to the other browser. Things you will need: Firefox and Chrome OneTab extension for Firefox and Chrome. Tip: you can check out our OneTab review for Chrome here. How to import tabs from Chrome to Firefox and vice versa Note: Please be advised that the following process will close all of your tabs and save the session to a list. But don't worry, you can restore the entire session just as easily. 1. Once you have installed the add-on, you should see its icon in the browser's toolbar. 2. Click on the button to open OneTab (this closes all open tabs) 3. Select the "Export/Import URLs" option on the right side of the page. 4. You should see an Import/Export tab that has a list of all the tabs that you had opened. It has the URL and web page title for each tab. 5. Copy this list to the clipboard. 6. Open Firefox and repeat steps 2 and 3. 7. Now you should be on the Import/Export tab. Paste the list of tabs from step 5 in the Import text field. 8. Click on the import button. OneTab should open a new tab which displays the tabs that you just imported. Click on the "Restore all" option, and the add-on should open all the tabs at once. You can also choose to restore only the ones that you want, by clicking on the tab titles individually. That's it. How simple was that? The process works the other way too, i.e., if you want to export tabs from Firefox to Chrome. Note that it is theoretically also possible to send the list of exported URLs to a contact. May be useful to share research or let someone pick off where you stopped. Another use for this method: Backup your sessions I use this method for a different purpose. Over the course of a week or two, I accumulate several dozens of sites in tabs that I find interesting or have opened for future research purposes. When I don't have the time to go through the list just yet but want to start fresh because the browser's tab bar gets convoluted, I use the extension to save the entire list of open sites in a text document. You can use the import option to restore the tabs anytime you want to. You can even backup your session, clear the browser's data and cookies and restore the tabs right back. This has been helpful for me quite a few times over the past few years. Note: OneTab hasn't been updated for a while on Chrome, but it still works perfectly. The Firefox version is updated frequently. There is an open source alternative for OneTab, called better-onetab, which I haven't used much since it was pulled and re-released by the developer. This post was inspired by something I saw on reddit's Firefox sub yesterday. It was an interesting post, but they used the developer console to move tabs from Chrome to Firefox and it also involved using two different extensions which made it a slightly more complex method. Source: How to import tabs from Chrome to Firefox and vice versa (gHacks)
  21. Here is the the score of browsers to see how much of HTML5 technologies and features they support. In order of highest to lowest. Edge insider Canary Version (Official build) canary (64-bit) Highest Score Google Chrome Canary Version 79.0.3924.0 (Official Build) canary (64-bit) FireFox version 71.0a1 (2019-09-26) (64-bit) Edge classic (EdgeHTML) Microsoft EdgeHTML 18.18990 Microsoft Edge 44.18990.1.0 Internet explorer 11 version 11.1.18990 Internet Explorer 11 (latest version) obviously has the worse score, but it's the only browser that can manage to get the perfect 100/100 score from Acid3 test among all these browsers tested. the rest of the browsers can only get 97/100. By the way, Acid3 is an old test. https://html5test.com/ http://acid3.acidtests.org/
  22. Mozilla will release a new Firefox version every 4 weeks from 2020 on Mozilla announced on September 17, 2019 that it will speed up the Firefox release cycle from 2020 onward for all Firefox channels. New Firefox versions get released every six to eight weeks currently after Mozilla switched to a variable release schedule in 2016. The browser maker started to ship new versions of the browser every six weeks in 2011 when it switched to a rapid release cycle. Mozilla uses a phased released system that moves new code from cutting edge Nightly versions of the browser through Beta and Developer editions before they reach the stable version and the majority of users. So-called Firefox ESR (Extended Support Release) versions are maintained for Enterprises and organizations that follow the same release cycle but with less frequent feature changes. Starting in the first quarter of 2020, Mozilla will release a new version of the Firefox web browser every four weeks. The organization wants to introduce new features including new Web APIs into Firefox more quickly. We’re adjusting our cadence to increase our agility, and bring you new features more quickly. In recent quarters, we’ve had many requests to take features to market sooner. Feature teams are increasingly working in sprints that align better with shorter release cycles. Considering these factors, it is time we changed our release cadence. Mozilla won't change the release cadence of Extended Support Releases. New ESR releases will be released every 12 months with a three month support overlap between soon-to-be-retired versions and the new ESR version. New ESR releases will be released every four weeks however instead of every six to eight weeks; the decision increases the number of ESR releases of a particular version of the browser, e.g. Firefox 68.x, however. A shortened release cycle has risks associated with it and Mozilla wants to maintain release quality and reduce these risks through careful planning, testing, quality management and staged rollouts. One of the planned changes increases the number of beta builds that Mozilla produces in a week up from two similarly to how Firefox Nightly updates are handled by the organization. Staged rollouts play an important role in the new strategy to help "minimize unexpected (quality, stability or performance) disruptions to our release end-users". The release cycle is moved slowly from the 6-8 week cycle that is currently used down to five and then four weeks over the next quarter and the first quarter of 2020. We have updated our Firefox release schedule overview to reflect today's announced changes. Closing words A four week release cycle is a massive undertaking for Mozilla; if the organization manages to keep up the quality of releases while introducing new features more quickly to the Firefox audience, it could be a win-win situation for everyone. ESR administrators will have to adjust to a faster release cycle as well but since the move to new major ESR versions remains the same, it should not be too problematic. Source: Mozilla will release a new Firefox version every 4 weeks from 2020 on (gHacks - Martin Brinkmann)
  23. Hello, As u all know, to create a website shortcut on your desktop, all you need to do is click on the website icon, drag and drop it on the desktop. I am using Firefox 69.0. I don't know if this issue began with the latest Firefox update or its was I who turned off a specific option in the settings. Does anyone know how to fix this issue ? Thank you
  24. FireMonkey uses Firefox's official API for userscripts and userstyles FireMonkey is a new browser extension for the Firefox web browser that enables users to manage userscripts and userstyles using the userscripts API that Mozilla introduced in Firefox recently. The extension offers similar functionality to established userscript extensions such as GreaseMonkey, TamperMonkey or ViolentMonkey as well as userstyle extensions such as Stylus on first glance. One of the core differences, at least right now, is FireMonkey's use of the new UserScripts API that Mozilla implemented in Firefox recently. Mozilla revealed that it created the API to address performance, reliability and security issues in regards to user scripts in Firefox. The API is designed to run userscripts in their own sandbox to isolate them; traditional extensions such as GreaseMonkey execute the scripts in the same process. Note: Mozilla changed the default behavior for userchrome.css and userContent.css files in Firefox 69. These files are not loaded by default anymore. Users need to enable the loading manually to restore the functionality. FireMonkey requests lots of permissions during installation; the developer explains why these are needed on Mozilla AMO. It requests the same permissions that other userscript extensions request. FireMonkey Current versions of Firefox support the UserScripts API. You can check whether that is the case in the following way: Load about:config in the Firefox address bar. Confirm that you will be careful. Search for extensions.webextensions.userScripts.enabled. If the preference is set to TRUE, it is enabled. A value of FALSE means it is not enabled. You may load userscripts and userstyles in the extension. The process is a manual one right now. Click on the extension icon and there on the add icons to add a new script or style to Firefox. You may also use the export and import options that you find in the extension's settings. Adding scripts or styles is not as comfortable right now as you need to copy the code, click on the add button, paste it before you click on save. Still, the process worked flawlessly when I tried it using scripts posted on Grease Fork. Options to save userscripts in disabled state or with auto-updating enabled are provided in the editor. You may edit userscripts and userstyles at any time using the extension. The extension supports GreaseMonkey GM3 and GM4 functions and functions provided by the Firefox API. Some scripts may not work properly when you create or import them; the Firefox API does not allow wildcard top level domains (TLD) which means that something like http*://www.google.*/* is not supported. It may be necessary to adjust scripts accordingly so that they may be imported without issues. FireMonkey comes with a Help file that explains differences and provides examples. It is a good place to start your investigation if something does not work as expected. The extension icon displays the number of scripts and styles that run on the active site. A click on the icon displays the active scripts and styles, and an option to disable or enable any with a single-click. The developer of the extension added a number of helpful features to the extension to improve management and identification of scripts. Script errors reference the name of the script in the console for improved identification and notifications from scripts display the script's name as well. Closing Words FireMonkey is a promising new extension for the Firefox browser that has a lot to offer even in the initial version. You can load, manage, edit, and create userscripts and userstyles using it, and it is using the new userscripts API that Mozilla will certainly put the focus on in the future. The extension would benefit from a few nice to have features, e.g. direct imports from other userscript extensions that are installed or recognition of the "install" button on popular userscript repositories. Source: FireMonkey uses Firefox's official API for userscripts and userstyles (gHacks - Martin Brinkmann)
  25. With Firefox 69 released and Firefox 70 entering beta, here are some fresh web browser benchmarks between Mozilla Firefox and Google Chrome from Ubuntu Linux. On the Firefox size, Firefox 68, 69, and 70 Beta were tested with and without WebRender being enabled and compared to Google's current Chrome 76 stable release. With the ARES-6 web browser performance there wasn't any measurable change between the Firefox releases tested while Google Chrome remained a great deal faster than Firefox on Linux for this benchmark. For the aging Octane benchmark, Firefox 69 and 70 Beta actually regressed the performance slightly compared to Firefox 68. Google Chrome 76 meanwhile was about 11% faster than Firefox 68. The WebXPRT benchmark is one of the few cases at least on the Linux desktop where Firefox beats out Google Chrome albeit by a small margin. With the Basemark browser benchmark there is a small boost in performance from having WebRender enabled but that is still beat out sharply by Google Chrome. JetStream is another one of the rare cases where Firefox beats out Chrome currently, at least from the Ubuntu 19.04 operating system stack. With CanvasMark, Chrome returns to offering its significantly faster performance on Linux. MotionMark is one of the benchmarks showing Mozilla's WebRender to its full potential. In addition, it shows the nice evolution of WebRender from Firefox 68 through the brand new Firefox 69 and the Firefox 70 Beta delivers another big step up in performance as it tries to eventually close the performance gap with Chrome. With the Speedometer benchmark the newer Firefox 68/70 builds were slightly faster than Firefox 68 but Chrome 76 still maintained a healthy lead. Lastly is the geometric mean of all the results shown in this article for the different browser benchmarks. Chrome 76 was 48% faster than Firefox 70 Beta but that shrunk to 25% when WebRender was enabled thanks to the healthy improvements found in the relevant benchmarks like MotionMark. There's still a ways to go for Firefox to close the performance gap on Linux with Chrome, but at least these Firefox 69 and Firefox 70 Beta benchmarks show progress is being made. Source
  • Create New...