Jump to content

Search the Community

Showing results for tags 'chrome'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Found 254 results

  1. Google Chrome 75.0.3770.100 Stable x64 https://www.google.com/dl/release2/chrome/AIQ1DKKlk7qg_75.0.3770.100/75.0.3770.100_chrome_installer.exe http://www.google.com/dl/release2/chrome/AIQ1DKKlk7qg_75.0.3770.100/75.0.3770.100_chrome_installer.exe https://dl.google.com/release2/chrome/AIQ1DKKlk7qg_75.0.3770.100/75.0.3770.100_chrome_installer.exe http://dl.google.com/release2/chrome/AIQ1DKKlk7qg_75.0.3770.100/75.0.3770.100_chrome_installer.exe https://redirector.gvt1.com/edgedl/release2/chrome/AIQ1DKKlk7qg_75.0.3770.100/75.0.3770.100_chrome_installer.exe http://redirector.gvt1.com/edgedl/release2/chrome/AIQ1DKKlk7qg_75.0.3770.100/75.0.3770.100_chrome_installer.exe x86 https://www.google.com/dl/release2/chrome/LzwKMTdw0w_75.0.3770.100/75.0.3770.100_chrome_installer.exe http://www.google.com/dl/release2/chrome/LzwKMTdw0w_75.0.3770.100/75.0.3770.100_chrome_installer.exe https://dl.google.com/release2/chrome/LzwKMTdw0w_75.0.3770.100/75.0.3770.100_chrome_installer.exe http://dl.google.com/release2/chrome/LzwKMTdw0w_75.0.3770.100/75.0.3770.100_chrome_installer.exe https://redirector.gvt1.com/edgedl/release2/chrome/LzwKMTdw0w_75.0.3770.100/75.0.3770.100_chrome_installer.exe http://redirector.gvt1.com/edgedl/release2/chrome/LzwKMTdw0w_75.0.3770.100/75.0.3770.100_chrome_installer.exe
  2. Prepare for a Google Chrome colour Explosion (New Tab Page) Google's Chrome web browser is not really a browser known for its customization options when it comes to the browser's user interface; that might change soon, however, as Google engineers began to work on a number of customization features some time ago. Work on the new customization options began in mid 2018 but first options did not become available until May 2019 when Google enabled first options in Google Chrome Canary. Google Chrome Canary is the cutting edge version of the Chrome web browser. It is a development version that is not suitable for production environments because of that. Chrome users could set different New Tab Page backgrounds back then but many of the other options were not available at the time. The release of Google Chrome 77.0.3828.0 changes that. The new version unlocks the interface colour customization menu and additional New Tab Page customization options. It is necessary to enable two experimental flags in Chrome Canary to unlock the new options. Here is how that is done: Load chrome://flags/#chrome-colours and set the flag to Enabled. Load chrome://flags/#ntp-customization-menu-v2 and set the flag to Enabled. Restart Google Chrome. Open a New Tab Page after the restart and activate the customize option on the page (the edit icon in the lower right corner of the page). Chrome opens the customize page with the three options Background, Shortcuts, and colour and theme. Background gives you options to pick a custom background image for the New Tab Page or, and that is a new option in Chrome 77, a solid colour. Solid colours are limited to the colours that Chrome displays when the option is selected; there is no option to pick a colour using a colour wheel or by entering colour codes like Vivaldi Technology does in its browser. The colour and theme menu is active in the new version of Chrome. You may use it to set different interface colour schemes in the Chrome web browser. Only four colour schemes are available at the time of writing. Just select one of the available options, e.g. pretty or bluish, to set a different interface colour scheme. The changes take effect immediately; you can click through all the available colour schemes to select the one that you like the most. Closing Words The only option that Chrome users had up until now was to install one of the available themes for the web browser. The new options that Google plans to integrate in the browser are still experimental in nature; it is possible, albeit unlikely, that these will get pulled and never make it into the release version of the browser. Google has yet to reveal when the changes will make it in a stable version of the web browser. Source: Prepare for a Google Chrome colour Explosion (New Tab Page) (gHacks - Martin Brinkmann)
  3. Google says the changes will improve performance and security. Ad block developers and consumer advocates say Google is simply protecting its ad dominance. Google has found itself under fire for plans to limit the effectiveness of popular ad blocking extensions in Chrome. While Google says the changes are necessary to protect the “user experience” and improve extension security, developers and consumer advocates say the company’s real motive is money and control. As it stands, the Chrome web store currently offers users a wide variety of ad blocking extensions that can help curtail the volume and nosiness of online advertising. From Adblock to Ghostery, such extensions make it harder for ad networks to build a detailed profile of your online activities or serve you behavioral ads based on your daily browsing habits. Last year, Google began hinting at some changes to Chrome’s extension system as part of its Manifest V3 proposal. Under these changes, Google said it would be modifying permissions and other key aspects of Chrome’s extensions system. The extension development community didn’t respond well, and said the changes would harm many popular user tools. Currently, many Chrome adblock extensions use Chrome's webRequest API, letting users block ads before they even reach the browser. But Google’s proposal would require extensions use the declarativeNetRequest API, which leaves it to the browser to decide what gets blocked based on a list of predetermined rules. While some extensions, like AdBlock, already use the latter, developers say the overall result will be tools that simply don’t work quite as well overall. In the wake of ongoing backlash to the proposal, Chrome software security engineer Chris Palmer took to Twitter this week to claim the move was intended to help improve the end-user browsing experience, and paid enterprise users would be exempt from the changes. Chrome security leader Justin Schuh also said the changes were driven by privacy and security concerns. Adblock developers, however, aren’t buying it. uBlock Origin developer Raymond Hill, for example, argued this week that if user experience was the goal, there were other solutions that wouldn’t hamstring existing extensions. “Web pages load slow because of bloat, not because of the blocking ability of the webRequest API—at least for well crafted extensions,” Hill said. Hill said that Google’s motivation here had little to do with the end user experience, and far more to do with protecting advertising revenues from the rising popularity of adblock extensions. “In order for Google Chrome to reach its current user base, it had to support content blockers—these are the top most popular extensions for any browser,” he said. “Google strategy has been to find the optimal point between the two goals of growing the user base of Google Chrome and preventing content blockers from harming its business.” Hill argues that the blocking ability of the webRequest API caused Google to yield some control of content blocking to third-party developers. Now that Chrome’s market share is greater, the company’s in a better position to “shift the optimal point between the two goals which benefits Google's primary business,” Hill said. Consumer advocates are similarly unimpressed, noting that the changes could also harm the effectiveness of some parental control, privacy, and security extensions. “This is a very bad decision on Google's part,” Justin Brookman, Director of Consumer Privacy and Technology Policy at Consumer Reports told Motherboard in an email. Brookman noted that millions of users rely on extensions like uBlock, Disconnect, and Ghostery to limit cross-site tracking and block malicious code from third-party servers, and that pushing these extensions to use a different API with lesser functionality would only weaken them. “It's hard to escape the suspicion that this is driven primarily by a desire to protect third-party tracking and ad revenue, where Google is the overwhelming market leader,” he said. “Notably, the move will insulate the largest ad blocker AdBlockPlus, who Google pays to whitelist their ads and tracking behavior.” That concern has long been mirrored by the Electronic Frontier Foundation. The group frequently argues that Chrome’s ad tracker blocking technology has lagged behind other browsers because Google, whose online ad market share currently hovers around 37 percent, doesn’t want to hamstring the profitability of tracker-driven, behaviorally-targeted ads. The EFF’s Privacy Badger extension is one of the ad blocking tools that would be impacted, and its development team has also spoken out against the changes. In an email, an EFF spokesperson argued that Google’s move would stifle developer innovation in the browser space and hamper user security and privacy. The group also wasn’t particularly sold on Google’s justification for the move. “Google's claim that these new limitations are needed to improve performance is at odds with the state of the internet,” the organization said. “Sites today are bloated with trackers that consume data and slow down the user experience. Tracker blockers have improved the performance and user experience of many sites and the user experience. Why not let independent developers innovate where the Chrome team isn't? The EFF says it was “particularly worrisome” that Google is going ahead with these changes despite all of the criticisms it's received from the developer community, adding that “security extensions should not be a privilege reserved only for enterprise users.” While Google has responded to criticism by saying the proposal was subject to change, it hasn’t yet backed off the proposal, which would be implemented this fall at the earliest. Should Google stick to its guns in the face of widespread criticism, it’s pretty clear that more than a few Chrome users will soon be on the market for a different browser. Source
  4. Fast forward: What's coming in future versions of Chrome? Every time Google updates its browser, it publishes release notes aimed at enterprises to highlight upcoming additions, substitutions, enhancements and modifications. Here's some of what's coming. geralt (CC0) Chrome gets fat while every other browser starves. Now with more than two-thirds of the world's browser user share - a measure of browser activity calculated monthly by metric vendor Net Applications - Google's Chrome has no peer in popularity. Its rivals are barely worth the name, with Microsoft's Edge so feeble that its maker decided to replace its internals with the same technology that powers Chrome and Mozilla's Firefox trying to hang on to just 10%. Not surprisingly, when Chrome speaks, everyone listens, whether about each browser upgrade - something Computerworld tracks in the What's in the latest Chrome update? series - and in what it plans to do in the near future. Every Chrome upgrade is accompanied by release notes aimed at enterprises that highlight some of the upcoming additions, substitutions, enhancements and modifications planned for the browser. We collected the most important for this "Coming soon" round-up. Just remember that nothing is guaranteed; Google points notes: "((These features)) might be changed, delayed, or canceled before launching to the Stable channel." Chrome 76: An end to opt-out of site isolation Unveiled in late 2017 within Chrome 63, Site Isolation is a defensive technology that segregates pages from different sites into different processes. Each process runs in a "sandbox" that restricts what the process can do, all part of a scheme to isolate malware from the browser as a whole and a device's over-arching OS. Site Isolation was enabled in stages until by mid-2018 it was enabled for virtually all Chrome users. At that point, only managed devices were able to opt-out. "((But)) starting with Chrome 76, we will remove the ability to opt out of site isolation on desktop using the SitePerProcess or IsolateOrigins policies," Google said. The end to opting out was to occur with Chrome 75, but was postponed to version 76, the upgrade scheduled to ship July 30. Google did not offer an explanation for the delay. Chrome 76: Flash to be blocked by default Two years ago, Adobe announced that it would finally bury Flash Player - the app that, in many ways, made the web - at the end of 2020. Browser makers like Google then explained how they would end their support for Flash. While Google has limited Flash for years - in late 2016, it was turned off by default and restricted to a handful of sites, including Amazon, Facebook and YouTube - this summer Chrome will institute a complete Flash blockade. With Chrome 76, Flash will be disabled by default. Individual users will be able to switch back to a default "Ask first" in settings (until Google ends all support by yanking it from the Chromium project in December 2020). And enterprises will be able to continue controlling Flash usage through the DefaultPluginsSetting, PluginsAllowedForUrls and PluginsBlockedForUrls policies. The toggle back to "Ask first" for Flash - which will let Chrome continue to run the Adobe plug-in but only after asking the user for each encountered Flash-equipped site - is in Settings, under "Privacy and Security," in the "Site Settings" selection. Click on "Flash," then in the next screen, on "Block sites from running Flash" to switch to "Ask first." Google When Chrome blocks Flash by default, users can switch the setting back to 'Ask first' - what it was prior to Chrome 76 - by clicking the toggle marked in red. Chrome 76: Lowering (the number of) flags "Many flags in chrome://flags will be removed in upcoming Chrome versions," Google said without detailing which will get the ax or even a rough number to be cut. "You should not use flags to configure Chrome because they are not supported. Instead, configure Chrome for your enterprise or organization using policies." The macOS version of Chrome 75 Stable listed 337 available flags and another 16 unsuitable for that operating system. Chrome ??: Chrome address bar searches return results from Google Drive "Soon, users will be able to search for Google Drive files that they have access to from the address bar," Google wrote. And that's all it wrote. However, it's possible to flesh out a bit more. In March, Google began testing integrations between Chrome and Google Drive for the G Suite Business, Enterprise, and Enterprise for Education productivity subscriptions. (The beta testing required Chrome 69 or later.) G Suite administrators can apply to join the beta project using the form submitted from this site. Previously, Google had pegged the debut of address bar searching of Google Drive to Firefox 75 - the version that launched last week - and seemed to imply that the feature would be available to all enterprise users, not just those running G Suite. Computerworld's testing of Chrome 75 Dev showed that enabling the option flag "Omnibox Google Drive Document suggestions" - displayed matches in the address bar of recently-accessed PDF and Google Docs/Sheets/Slides. That setting, which can be accessed from the chrome://flags page, appeared in the Stable version of Chrome 75, hinting that it's about ready for real-world use. It's unclear whether the in-address-bar searching of Google Drive contents will be available only for G Suite users or for all those who have stored content in Google Drive. Computerworld's take? Because of a line in the beta description - "This goes beyond current functionality, which lets users search for Google Drive files that they have recently accessed" - we think that the tool will be only for G Suite customers. Source: Fast forward: What's coming in future versions of Chrome? (Computerworld - Gregg Keizer)
  5. Google Chrome users may soon get additional customization options to change the default functionality and layout of the browser's New Tab Page. Chrome users who want to modify the New Tab Page currently don't find many options to do so. The best option for many is to download a New Tab Page extension to customize what is displayed on the page. Google has been working on New Tab Page customization improvements for a while. Recent modifications are now available in Chrome Canary, the cutting edge version of the Chrome browser. The changes are not fully implemented at this point but they provide an outlook of things to come. The options are hidden behind experimental flags at the time; users who want to follow their development need to enable them in Chrome Canary: Load chrome://flags/#ntp-customization-menu-v2 in the Chrome address bar and set the flag to Enabled. Load chrome://flags/#chrome-colours in the Chrome address bar and set the flag to Enabled. Restart the Chrome browser. Chrome customization menu Open the New Tab Page after the restart and activate the customize option on that page to open the redesigned customization menu. The Shortcuts section is not fully functional yet but it highlights Google's intention clearly. Chrome users get options to select the type of shortcuts that they would like to see on the New Tab Page. My shortcuts -- The shortcuts are displayed based on the frequency of visits and selected by Chrome. Most visited sites --Shortcuts are curated by the user. The wording of both options seems confusing but it is a development version and Google is probably going to address this before release. The third and final option is to hide any shortcuts on the New Tab Page. Chrome colours The colour and Theme section of the customize page is not active yet either. The option shows a blank page when you select it currently. My best guess is that you will be able to change colour and theme of the New Tab Page once the change lands in Chrome. Background is still available to select a custom image for the New Tab Page using a local or Google provided image. An option to set no background image is provided as well. Closing Words It is unclear when these changes will land in Chrome Stable. There is still a chance that some or all will be dropped; but that is true for all experiments that Google adds to the browser using the chrome://flags page. The customization options that Chrome offers currently are inferior to those offered by other browsers such as Mozilla Firefox, Opera, or the Vivaldi browser. Source: Google Chrome's New Tab Page may soon get a customization boost (gHacks - Martin Brinkmann)
  6. 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)
  7. Every time Google updates its browser, it publishes release notes aimed at enterprises to highlight upcoming additions, substitutions, enhancements and modifications. Here's some of what's coming. geralt (CC0) Fact: Chrome rules. With a massive two-thirds of the world's browser user share - a measurement of browser activity calculated monthly by analytics vendor Net Applications - Google's Chrome has no peer in popularity. So when Chrome speaks, people listen. That holds true for whatever moves Google makes with each browser upgrade - something Computerworld details in the What's in the latest Chrome update? series - and in what it plans to do in the future. With each update, Google publishes a set of release notes aimed at enterprises. In those release notes, the company highlights some of the upcoming additions, substitutions, enhancements and modifications planned for its browser._ In an effort to look ahead at the browser's future, we've collected the most important of the latest items in Chrome's "Coming soon" category. But as Google takes pains to point out, "They might be changed, delayed, or canceled before launching to the Stable channel." You've been warned. Chrome 75: Chrome address bar searches return results from Google Drive "Users will see Google Drive results when entering a search in the address bar, including PDFs, Google Sheets, Docs, and Slides," Google wrote. And that's all it wrote. However, it's possible to flesh out the expected feature. Google in March kicked off testing of integration between Chrome and Google Drive for the G Suite Business, Enterprise, and Enterprise for Education productivity subscriptions. (That beta testing requires Chrome 69 or later.) The upcoming address bar-search is somewhat different. Computerworld's testing of Chrome 75 Dev – after enabling the option flag "Omnibox Google Drive Document suggestions" – showed that suggested matches surfaced in the address bar only of recently-accessed PDF and Google Docs/Sheets/Slides. In other words, the Chrome 75 feature seems a subset, although not a perfect one, of what's already in testing for G Suite subscribers, but will be available to all Chrome users who have content in Google Drive. Google Chrome 75 will suggest results from Google Drive for documents that have been recently accessed. Chrome 75: End to opt-out of site isolation Unveiled in late 2017 within Chrome 63, Site Isolation is a defensive technology that segregates pages from different sites into different processes. Each process runs in a "sandbox" that restricts what the process can do, all as part of a scheme to isolate malware from the browser as a whole and the device's over-arching OS. Site Isolation was enabled in stages until by mid-2018 it was enabled for virtually all Chrome users. At that point, only managed devices were able to opt-out. As of Chrome 75 - currently scheduled to ship June 4 - that will end. "We've resolved the reported issues and starting with Chrome 75, we will remove the ability to opt out of site isolation on desktop using the SitePerProcess or IsolateOrigins policies," Google said. Chrome 75: Version roll-back Google will add a browser roll-back process for enterprises that want to retreat to an older version of Chrome, the company said as it named the target. "Chrome 75 on Windows will include a policy that allows administrators to roll back to a previous version of Chrome," Google said. The functionality will be available only to customers using Windows' group policies to manage Chrome. "Add a RollbackToTargetVersion app policy to allow enterprise administrators to enable rollback in conjunction with the existing TargetVersionPrefix policy," Google stated. The most likely reason for wanting to roll back Chrome to an earlier version would be because the latest browser caused problems, perhaps a mission-critical app compatibility or workflow issue. Google was adamant that a roll-back should be a last-ditch effort by enterprise IT. "This policy is meant as an emergency mechanism and should be used with caution," the company said. "If you roll back to an earlier version, you will expose your users to known security issues. Use this policy at your own risk." Google also urged that customers turn on the browser sync feature or alternately, Roaming User Profiles, which lets users take bookmarks, passwords, extensions and preferences to multiple PCs. Failing to do that will mean data synced from later versions won't be usable by older editions. A later version, Google added, will "improve the rollback experience by preserving user states during the rollback process" so that sync and roaming profiles won't be needed. Chrome 76: Flash to be blocked by default Nearly two years ago, Adobe announced that it would finally bury Flash Player - an app that in many ways, made the web - at the end of 2020. Browser makers like Google then detailed how they would end their support for Flash. While Google has limited Flash for years - in late 2016, it was turned off by default and restricted to a handful of sites, including Amazon, Facebook and YouTube - this summer Chrome will institute a complete Flash blockade. With Chrome 76, now slated to ship July 30, Flash will be disabled by default. Individual users will be able to switch back to a default "Ask to use Flash" in settings (until Google ends all support by yanking it from the Chromium project in December 2020), and enterprises will be able to continue controlling Flash usage through the DefaultPluginsSetting,PluginsAllowedForUrls and PluginsBlockedForUrls policies. Source: Fast forward: What's coming in future versions of Chrome? (Computerworld - Gregg Keizer)
  8. What Is Lazy Loading and How to Enable It in Google Chrome 74 Google Chrome 74 is now available for download on all supported platforms, and in addition to a dark theme for Windows 10 (which is currently rolling out to devices in stages), it also introduces a series of other improvements and security fixes. One under-the-hood addition that many users might not be aware of is called lazy loading, and it is supposed to make page loading faster in Google Chrome. What’s important to know, however, is that lazy loading is still considered an experimental feature at this point, so it’s not enabled by default in Google Chrome 74. There’s a chance that Chrome 75 would activate it for all users, but for the time being, you need to turn it on manually in the browser. What is lazy loading? The concept of lazy loading isn’t necessarily new, but it’s the first time Google makes it available for users running the stable version of Chrome browser. In just a few words, lazy loading allows the application to load only critical page content that you need, and only then load additional resources when scrolling to them. This way, the page actually loads faster and avoid unnecessary downloads and bandwidth use because, technically, a browser without lazy loading would pretty much download all content even if you might not need or access it. Google explains the following the developer documentation on lazy loading: “Lazy loading is technique that defers loading of non-critical resources at page load time. Instead, these non-critical resources are loaded at the moment of need. When we lazy load images and video, we reduce initial page load time, initial page weight, and system resource usage, all of which have positive impacts on performance. Used with care, lazy loading images and video can seriously lower the initial load time and page payloads on your site. Users won't incur unnecessary network activity and processing costs of media resources they may never see, but they can still view those resources if they want. As far as performance improvement techniques go, lazy loading is reasonably uncontroversial. If you have a lot of inline imagery in your site, it's a perfectly fine way to cut down on unnecessary downloads.”How to enable lazy loading in Google Chrome 74While it’s still an experimental feature, you can enable lazy loading in the latest stable version of Google Chrome and try out yourselves to determine if any speed increase is noticed when loading sites. Doing this is quite easy. First of all, launch the browser and in the address bar, type the following command: chrome://flags Then, you need to enable the following two flags in the browser: Enable lazy image loading Enable lazy frame loading To find then faster, you can copy the following codes and paste them in the address bar of Google Chrome: chrome://flags/#enable-lazy-image-loading chrome://flags/#enable-lazy-frame-loading Both of these two flags are currently set to Default mode, which means they are disabled, so just click the drop-down menu and then switch them to Enabled. Reboot your browser and the feature should technically be up and running in your browser. Keep in mind, however, that developers need to manually enable lazy loading on their websites, so it could take a while until the web is ready for this new feature. However, you can already try out this feature in Chrome 74, albeit I expect this push to become more widely adopted by the time the next version of Chrome gets the green light. Google Chrome 75 is projected to launch on June 4, while the first beta should go live between May 2 and May 9. Source
  9. 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
  10. Microsoft's Chromium-based Microsoft Edge web browser has not been released yet as a stable version; the preview versions that Microsoft released, Microsoft Edge Dev and Canary, provide a good understanding of the browser already, however. The web browser relies on the same core that Google Chrome uses, and that makes these browsers look and behave similarly in most aspects. That's good on the one hand, as it means faster updates and better web standards compatibility, but it also means that there is little that distinguishes the browser from Chrome unless modified. Companies that rely on Chromium can modify the browser; Vivaldi, Opera and Brave do this to create custom experiences that differ significantly from Chromium and Google Chrome. Microsoft's Edge browser will be different to a degree as well, and the following list of features highlights just some of the differences between Edge and Chrome. 1. Better Support for commercial Streaming Media services Microsoft Edge is the only Chromium-based browser that supports Google's Widevine DRM and Microsoft's own PlayReady DRM. Support for the latter unlocks 4K streams on Netflix, something that only Internet Explorer and Microsoft Edge (classic) support on Windows. Chrome, Firefox, and any other browser may stream with a quality of up to 1080p with the help of extensions. The feature is restricted to Windows 10, however. 2. Internet Explorer Mode The Chromium-based version of Microsoft Edge will (likely) come with Internet Explorer integration. The feature is listed as an experimental flag at this time which could mean that it is removed without further notice. It is more likely that the feature remains in Edge once it gets released to provide organizations with an option to access Internet Explorer optimized or exclusive content in Edge. The feature is not completely integrated right now but the description suggests that Edge users may load Internet Explorer content in a tab in Edge. 3. Support for Microsoft Voices Another feature that is hidden behind a flag currently. Enable Microsoft Voices Extension adds support for Microsoft voices in the SpeechSynthesis API. Interestingly enough, the feature is available for Windows, Mac and Linux devices. 4. Mute Tab instead of Mute Site Microsoft Edge supports tab muting. You can mute individual tabs using its default configuration which gives you more control over the muting process. Chrome supported this in previous iterations as well but Google changed the feature to site muting instead. If you mute a site in any tab, that site gets muted everywhere automatically in Chrome. In Edge, just click or tap on the sound icon in front of the page title in the tab to mute audio in that tab. Microsoft Edge still supports site permissions to mute audio permanently for individual domains. A flag is available to enable site-wide muting. Load chrome://flags/#edge-sound-content-setting to configure it. 5. Windows Defender SmartScreen integration Chrome and most Chromium-based browsers use Google's Safe Browsing security feature for security. Microsoft Edge will use Microsoft's Windows Defender SmartScreen security feature instead. The feature protects against malicious sites and downloads. Just like Google's implementation, it is known for the occasional false positive. Can be disabled in the settings. 6. Microsoft Account and Azure Active Directory support It should not come as a surprise that the Chromium-based Microsoft Edge web browser will support Microsoft Account and Azure Active Directory for authentication and single sign-in. Edge supports Microsoft infrastructure better than Chrome, and integration of these features confirms that. 7. Removed Google services Microsoft published a list of disabled or removed Google services in the Chromium-based Edge browser recently. The list of features is surprisingly long; Microsoft disabled some and replaced others (or plans to), e.g. Google Translate will be replaced by Microsoft Translate. While you could say that you trade one data-hungry company for another, it boils down to personal preference. 8. Exclusive Extensions Microsoft Edge users may install extensions from the Chrome Web Store or Microsoft's only store. The main advantage of this is that Microsoft's store does not have the same restrictions as Google's store. One example: Google disallows extensions that download videos from YouTube, Microsoft's Store does not. It is true, however, that Microsoft's Store lists a bit more than a 100 extensions at the time. It seems unlikely that many more will be added to the Store in the coming years if you consider the rather weak number of extensions that were produced for Edge or ported since 2015. Source: 8 ways in which Microsoft Edge (Chromium) is better than Google Chrome (gHacks - Martin Brinkmann)
  11. If you use the multimedia keys on your computer keyboard to control playback in apps such as Spotify or iTunes, you may notice that functionality stopped with the release of Chrome 74. Google introduced support for keyboard multimedia keys in Chrome 73; Chrome users may use the functionality to control playback on YouTube and other sites that make use of the Media Session API. On YouTube, you can pause, start and stop playback, change the volume, mute, or jump forward or backward using media keys. The release of Chrome 74 may block other sites from working correctly with multimedia keys. The change affects "other" processes that may make use of media keys; if you run Spotify or iTunes on the desktop, or another other media application that supports multimedia keys, you may notice that the keys don't function properly anymore if Chrome is running. It appears that Chrome is blocking other apps from using media keys. One solution for the issue is to close Chrome completely whenever you want to use an application that supports media keys. It is not the most practicable of solutions as it is not very comfortable and limits how you use the computer as you cannot use Chrome and any of these applications side by side anymore. Disabling Chrome's Multimedia Key handling Google Chrome comes with a flag currently that controls the browser's hardware media key handling. Flags are experimental features that let you control certain features in Chrome. Google may remove flags at any time. You may disable the Hardware Media Key Handling flag in Chrome currently to prevent Google Chrome from restricting media keys access. Here is how that is done: Load chrome://flags/#hardware-media-key-handling in the Chrome address bar; this should open the right flag when loaded. Set the Hardware Media Key Handling flag to Disabled. Restart Google Chrome. Change the status of the flag to Default or Enabled if you want to restore the default. Note that Chrome won't accept media key input anymore if you set the status to disabled. Google plans to release Chrome 74 Stable on April 23, 2019. Source: Fix Chrome blocking keyboard multimedia keys from working (gHacks - Martin Brinkmann)
  12. NoScript extension officially released for Google Chrome After more a decade, NoScript is finally available for Chrome users. Starting today, the NoScript Firefox extension, a popular tool for privacy-focused users, is also available for Google Chrome, Giorgio Maone, NoScript's author, has told ZDNet. The NoScript Chrome port, on which Maone has worked for months, is now available from the official Chrome Web Store, via this link. USERS HAVE BEEN ASKING FOR A CHROME PORT FOR YEARS NoScript's availability for Google Chrome will make many people happy. The extension has a mythical status among privacy-minded users, who have dogged Maone for a Chrome version for years. The original Firefox add-on was launched on May 13, 2015, to rave reviews. At the time, it was introducing a novel concept that a browser add-on could intercept and block the loading or execution of dangerous or unwanted JavaScript code. The extension gathered a huge following across the years, and because of its unique features, it has also been selected as one of the very few add-ons that come built into default installations of the Tor Browser. It is also one of the most-used and must-use extensions in the arsenal of security researchers that visit sites with malicious code, as the extension can prevent the execution of some exploits. It's for these reasons that users have been asking Maone for a Chrome port for years. NOSCRIPT FOR CHROME FACED SOME DEVELOPMENT HURDLES Work on the Chrome version started last year after the original NoScript for Firefox version was ported from the old Firefox XUL API to the more modern WebExtensions API, which is compatible with both Firefox and Chromium extensions systems. Everything almost fell apart in January this year, when Chrome engineers were planning to roll out a set of features that would have killed not only NoScript's ability to do its job, but also ad blockers and other similar extensions that needed to interact with JavaScript resources. Google backtracked on some of its proposed changes following a huge backlash from both users and extensions developers, and today we have the first version of NoScript for Chrome. Nonetheless, Maone still fears that some of Google's planned changes, even in their current form, will still eventually impact NoScript in the long-run. "I and other worried developers are [still] lobbying Google to rethink this plan," Maone told ZDNet today. "Some concessions have already been done, but I'm also studying alternative approaches for the worst case scenarios." But in spite of some looming problems, the Chrome port is almost identical with the Firefox (Tor Browser) version, in terms of blocking/whitelisting abilities, and settings section. NOSCRIPT'S XSS PROTECTION NOT AVAILABLE IN CHROME VERSION "Talking about differences across supported browsers, the code base is now is exactly the same," Maone told ZDNet. "But on Chromium, I had to disable, at least for the time being, NoScript's XSS filter." Below is an image of NoScript's XSS filter showing an alert in the Tor Browser, a feature not available in the Chrome version, according to Maone. "Chromium users will have to rely on the browser's built-in 'XSS Auditor,' which over time proved not to be as effective as NoScript's 'Injection Checker'," Maone told us. "But the latter could not be ported in a sane way yet, because it requires asynchronous processing of web requests: a feature provided by Firefox only. "To be honest, when Firefox switched to the WebExtensions API, which was largely inspired by Chrome, Mozilla made me contribute to its design and implementation in order to ensure that it supported NoScript's use cases as much as possible," Maone said. "Regrettably, the additions and enhancements which resulted from this work have not been picked up by Google." A STABLE RELEASE EXPECTED IN JUNE Currently, NoScript for Firefox has over 1.5 million users, and the expectation is that the Chrome version will pick up even a bigger following due to Chrome's larger userbase. "I'm very satisfied of this first public Chromium-compatible NoScript's beta (10.6.x). I plan to bless NoScript 11 as a 'stable release for Chrome' by the end of June," Maone told ZDNet. "I feel the urge to thank the awesome folks at the Open Technology Fund for the huge support they gave to this project, and before that to NoScript's WebExtension migration," Maone added. "And I'm excited that under the same umbrella Simply Secure will start working next week on improving NoScript's usability and accessibility." Source
  13. Microsoft Confirms Google Chrome, Microsoft Edge for Windows 10 ARM One of the benefits of Microsoft’s transition to Chromium is that Google itself has become more interested in bringing its apps and services to Windows 10. And Windows 10 ARM as a platform is likely to get several improvements only thanks to this, as Microsoft worked together with Google engineers to prepare the Chromium engine for ARM-based devices. Earlier this week, developers managed to get Google Chrome up and running on Windows 10 ARM, which in turn made it possible to install the browser on Windows phones powered by this OS version too. With Edge preview finally becoming available for download, Microsoft confirms that Chromium on Windows 10 ARM is something the company has been working on and further announcements on this should follow later this year. “We’ve been collaborating with Google engineers to enable Chromium to run natively on Windows on ARM devices starting with Chromium 73. With these contributions, Chromium-based browsers will soon be able to ship native implementations for ARM-based Windows 10 PCs, significantly improving their performance and battery life,” the Microsoft Edge team announced.Touch support in ChromiumAdditionally, Microsoft says it was focused specifically on optimizing the browser for Windows 10 devices, and adding touch support was a priority given this input method is a key part of the experience with the operating system. “To help our customers with touch devices get the best possible experience, we’ve implemented better support for Windows touch keyboard in Chromium, now supporting touch text suggestions as you type and “shape writing” that lets you type by swiping over keys without releasing your finger,” it says. There is no ETA available right now as to when Chromium browsers would land on Windows 10 ARM, but both Google and Microsoft could be working on such versions of their browsers. Most likely, additional details would be shared at the Build developer conference next month. Source
  14. 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
  15. Google Chrome on Windows Phones Is a Real Thing Now Microsoft giving up on EdgeHTML and migrating to Chromium produces a series of benefits, including Google itself being more willing to support Windows as a platform. For example, one of the projects that could see daylight as a result of Microsoft’s commitment to Chromium is a Windows 10 ARM version of Google Chrome browser. And by the looks of things, this is already a work in progress, and a software developer managed to get the browser up and running on Windows 10 on ARM. Jeremy Sinclair explains in a tweet that it’s actually possible to build Google Chrome for Windows 10 ARM, even though not all features are currently working exactly as expected, as it’s the case of the emoji window in Windows 10. “BEHOLD! Successful Chromium build completed and is running on Windows ARM64 \o/! It was SUPER fast opening, also,” he tweeted. Such an achievement brings in its turn several other benefits, such as the possibility of running Google Chrome on other Windows 10 on ARM devices. Included Windows phones, that is.Chrome on Windows phones, a dream that finally comes trueNot a long time ago, the developer community managed to install Windows 10 ARM on Windows phones, like the Lumia 950 XL, so thanks to this new project, Google Chrome should be running on these smartphones as well. “A windows phone running chrome natively, rare endangered species in an unnatural habitat,” software developer Gustave Monce tweetedduring the weekend. As I said on several occasions, while it’s nice to see software like Windows 10 on ARM or Google Chrome running on Windows phones, Microsoft’s smartphone platform is dead anyway. The company will stop providing updates in December this year, so no further security improvements would be released. Additionally, Microsoft itself recommends users to switch to Android and iOS to enjoy the full benefits of its apps. Source
  16. Use Google Chrome as a Media Player on Windows 10 Google Chrome is currently the number one browser on the desktop and mobile, and the latest updates bring more improvements that further enhance the experience when browsing the web. But at the same time, there are features in Google Chrome that allow the app to step beyond the typical web browsing purpose and actually help users perform tasks that they didn’t normally expect in such an app. One of them is playing video files that are stored locally and which typically requires a multimedia player installed on the device. Technically, with Google Chrome you can not only play videos stored on the local drives, but also watch them using the built-in Picture-in-Picture mode that makes it possible to keep the video playing while doing something else on the screen. The PiP mode is already available in Google Chrome and in a series of other browsers, and it will also be part of the upcoming Chromium-based Microsoft Edge. Obviously, since it’s not a fully-featured file manager or multimedia player, watching locally-stored video files in Google Chrome isn’t necessarily a straightforward thing to do, albeit it’s still possible with a few clicks. As per TechDows, you first need to know the full path to your file and only then open it in Google Chrome. First and foremost, just make sure that you’re running one of the latest Google Chrome versions – for Picture-in-Picture Chrome version 70 and newer is required. Then, you need to browse to location where your file is stored. In my tutorial here, I use a file called sample.mp4 and stored in the Downloads library. While you can manually type the full path to the file, it’s much easier to simply copy it with a simple trick. Navigate to its location, then press Shift + right-click on the file > Copy as path. This option only copies the path to the file to the clipboard, so when you paste it, you’ll get the full address. Once the path to the file is copied to clipboard, you need to head over to Google Chrome to open it. Just paste the path in the address bar and remove the quotes at the beginning and the end of the path. Press enter and the video should then be loaded in the browser. At this point, you’re already using Google Chrome as a media player, and you can watch the video just like you’d normally do with a multimedia player. But as I said earlier, there are additional options available in the browser and which you can use to further enhance this video watching experience. And one of them is the said Picture-in-Picture mode. To activate this video mode, simply right-click the video > Picture in Picture ­– if you’ve used this feature before, you probably know that on sites like YouTube, you need to right-click the video twice in a row; however, this isn’t required for videos stored on the local drives because there’s no other context menu that launches on the first click. Once you click Picture in Picture, the video should then start playing in a smaller window placed in the bottom right corner, and you can drag it around the screen, resize it, pause or close it. There are no other extra and unnecessary features, and everything works pretty smoothly all the time. The same trick would work in all Chromium-based browsers, including the upcoming Microsoft Edge, and you can try it out already by downloading the leaked buildavailable here – an official preview version of Microsoft Edge is expected shortly. Source
  17. How to Fix Screen Flickering in Google Chrome on Windows 10 Version 1809 The latest version of Windows 10 and the newest Google Chrome release seem to be an unfortunate mix of software for some users, as the browser is impacted by a super-annoying screen flickering bug that makes it completely unusable. At this point, it looks like the issue is only experienced on Windows 10 version 1809, also known as October 2018 Update, when running Google Chrome version 73. However, I’m seeing reports that other versions of Chrome could be affected too. A thread on the Google Chrome Help forums indicate that a potential solution to this glitch could be disabling hardware acceleration in the browser. However, as many of the users seeing the screen flickering discovered, the hardware acceleration feature doesn’t seem to be in any way connected to the bug. So the problem resides in a different place. A post on the said forums and coming from a Google Platinum Product Expert indicates that the screen flickering may be generated by a compatibility issue with one or two Windows 10 features. This also confirms that the problem is exclusive to Windows 10 and not happening on Linux and macOS. Basically, the post indicates that the flickering is caused by the Windows Slideshow feature or by the automatic color selection in the operating system. “At the moment, I don't know why these two settings cause your screen to flicker in Chrome. Once I know more, I'll let you know,” the post notes. What’s important to keep in mind is that Google hasn’t yet officially acknowledged the bug, but since a fix already exists, there’s a good chance the development team is looking into it and a patch would be released soon. So technically, the workaround is to disable the Windows Slideshow and the automatic color selection in the operating system. Here’s how to do both. First and foremost, you need to head over to the Settings screen. For the slideshow, this is the path that you need to follow: Settings > Personalization > Background If the current setting on your device is Slideshow, you need to click the drop-down menu and choose between Picture and Solid color. Both of them do the job, so choose whatever works for you and see if the screen flickering is gone. If it’s not, you need to disable the automatic color section too. To do this, the Settings app is again the one that you need to use, so launch it and then follow this path: Settings > Personalization > Colors > Choose your color Look for an option that is called Automatically pick an accent color from my background and make sure it’s disabled. Again, check to see if the screen flickering is still there. For the time being, no other workaround seems to exist, so if you really insist on using the aforementioned Windows 10 features, there’s not much to do about it. Google Chrome is currently the world’s number one browser on the desktop, and given that the adoption of Windows 10 also grows every month, there’s a high chance that this issue could hit a large number of users. However, judging from the number of complaints posted online, it’s not yet a widespread bug, though it goes without saying that Google should resolve it as soon as possible. The next Google Chrome stable release is version 75, and it is projected to launch on all supported platforms on April 18. It remains to be seen, however, if a fix for this bug would be included in this update. Source
  18. Three Reasons Chromium Microsoft Edge Can Be Bigger than Google Chrome Despite being the world’s number one desktop browser for a long time, Internet Explorer has never been everyone’s favorite browser, and the massive improvements that Google and Mozilla released for Chrome and Firefox provided users with alternatives that many embraced. Microsoft introduced Edge browser with much fanfare in Windows 10, promising a truly powerful rival to the likes of Chrome and Firefox. Eventually, Edge turned out to be just another failed experiment, and despite the more or less significant improvements released as part of new Windows 10 feature updates, the new browser eventually failed to make any difference. So in late 2018, Microsoft announced another major change in this regard, as it decided to migrate Microsoft Edge from the EdgeHTML engine to Chromium. This is the same engine that powers Google Chrome and a series of other browsers like Vivaldi. At first glance, switching to Chromium is seen by many as living proof that Microsoft can’t succeed in the browser market on its own. But after trying out the unofficial preview build of Edge browser, it becomes more obvious that Microsoft Edge can finally become a leading browser on both the desktop and mobile. All Google Chrome featuresFirst and foremost, because it’s based on Chromium, Microsoft Edge technically has all the features of Google Chrome, and Microsoft can give its own touches to each update to specifically tailor it to match its own user base. In other words, Microsoft Edge would no longer lag behind rivals when it comes to features, and long-time Windows users certainly know how important this is. Google Chrome is currently the leading browser worldwide, and there’s a good reason for this. The feature lineup plays a key role in the overall feature package, and now Microsoft Edge can score big in this regard as well.Finally available cross-platformThe Chromium engine also allows Microsoft to release Edge on more platforms than just Windows 10. This means the company can significantly increase the number of users running its browser, as Edge would offer support for Windows 10, Windows 8.1, and Windows 7, but also for macOS and Linux. Windows 10 and Windows 7 are currently the world’s most popular desktop operating systems, and despite the latter reaching the end of support in January next year, it’s still a widely-used platform across the world. So there’s no doubt that by making Edge available on Windows 7, Microsoft not only that wins more users, but it can also convince some to upgrade to Windows 10 and enjoy the benefits of native integration. Just like Google Chrome, Microsoft Edge is also available on mobile, and Microsoft releases updates for both Android and iOS versions on a regular basis.The world’s largest distribution platformOne of the biggest advantages over Google Chrome is that Microsoft Edge would benefit from the largest distribution platform on the desktop. It’s Windows itself, and Microsoft not only that will offer Edge as the default Windows 10 browser, but it’ll also encourage users running older versions of the OS to replace Internet Explorer (or other browsers) with its new app. Windows 10 has already become the number one desktop operating system after it managed to overtake Windows 7 a few months ago, and the target for Microsoft is to bring it to 1 billion devices worldwide. This means Microsoft Edge would come pre-installed on 1 billion devices, and while not everyone would stick with it, the opportunity to target such a large audience is huge. Microsoft is projected to release the new Edge browser later this year, but a preview build should go live any day now. An unofficial Microsoft Edge version is already up for grabs if you want to try it out. Source
  19. First image surfaces of Google Chrome's upcoming Tab Groups feature Work on Tab Groups is still in its early phases. Feature won't be ready for months. Image: Bret Sepulveda Four months after Google engineers started working on the feature, today we have the first image of Chrome's upcoming Tab Groups UI. The feature was one that was sadly lacking in Chrome, and one that some users will greatly appreciate. As portrayed in the image above and as its name hints, Chrome Tab Groups will let users organize tabs together, in multiple groups, allowing for a much greater level of control for messy Chrome users who work with tens of tabs at a time. To be clear, the feature is still a long way from being finished, and this is just a screenshot released by a Chromium engineer. Current versions of Chrome Canary, Google's testing playground for upcoming Chrome features, don't yet support the new interface. The only Tab Groups-related functionality implemented in Chrome Canary right now is a right-click menu that sometimes loses tracks of tabs and their respective groups. However, most of the Tab Groups development over the past few months has been on creating the codebase on which the UI will work. If Chrome users want to be on the forefront of Tab Groups testing, they'll need to install Chrome Canary, visit the chrome://flags page, and enable the Tab Groups option. Until a stable version of Tab Groups lands in Chrome, users who have a habit of working with more tabs than they can handle will have to rely on third-party extensions currently available on the Chrome Web Store --or use other browsers. Vivaldi, a web browser based on Chromium, the same engine at the heart of Google Chrome, already supports Tab Groups functionality, although in a different manner, using a concept first seen in older Opera versions. Tab stacking feature in Vivaldi Firefox used to have a Tab Groups feature, but Mozilla removed it from its code after telemetry showed that very few users were using it and supporting its codebase became too costly for the Firefox devs. Knowing of Tab Groups' demise in Firefox questions Google's decision to start working on such a feature in the first place, but user feedback has been mostly positive, until now. Source
  20. How to Launch Google Chrome in Incognito Mode by Default Google Chrome continues to be the world’s number one desktop browser, and there’s no doubt it all happens for a good reason. And while even the software giant Microsoft is migrating to Chromium, the engine that powers Google Chrome, there are several features that users hope to get in a future update for the browser. One of them is an option that would make it possible to use Google Chrome in Incognito mode by default, technically launching the browser with this private browsing feature and not leaving any traces behind no matter what. First of all, let’s see what Incognito mode means. When this browsing mode is enabled, Google Chrome doesn’t save browsing history, cookies, site data, and information entered in forms. However, it’s important to know that some data isn’t hidden from websites you visit, and information like the IP address is still collecting. Right now, there’s no option to launch Google Chrome with the Incognito mode enabled by default, and the only way to do this is to first fire up the browser and then manually click the Menu button > New Incognito Window. However, there are two ways to do this, though each comes with its very own setbacks. So stay with me as I detail both. The first method is also the one that’s the easier to use, as all you have to do is to modify the launch parameter to run the browser in the Incognito mode. Basically, you first need to create a shortcut of Google Chrome anywhere you like – for this tutorial, I used the default Google Chrome installation path and created a shortcut on the desktop. Next, you need to right-click the Google Chrome shortcut > Properties. The Target field under Shortcut is the one we’re going to use. By default, it looks like this: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" So what we need to do is to add the -incognito parameter at the end to make it look like this: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -incognito The next time you launch Chrome using this shortcut, it should run in Incognito mode automatically. The main drawback is that you need to either remove the added parameter or to manually create a new standard browsing window, so I recommend you to create separate shortcuts for each mode. The second method involves editing the run patch of Google Chrome in the Registry Editor. To do this, launch the Registry Editor by typing regedit.exe in the Start menu. Navigate to the following location: HKEY_CLASSES_ROOT\ChromeHTML\Shell\open\command Double-click the Default entry in the Windows Registry Editor, and change it from: "C:\Program Files\Google\Chrome\Application\chrome.exe" "%1" to: "C:\Program Files\Google\Chrome\Application\chrome.exe" -incognito "%1" Close the Registry Editor and that’s pretty much it. The next time you launch Google Chrome, the Incognito mode should be enabled by default and no data should be collected. Just like in the case of the first method, you need to manually change the registry key or open a standard browsing window. The biggest setback of both methods is that they enable the Incognito mode when manually launching the browser, but not when clicking on links. For example, if you receive a link in an email and Google Chrome is configured as the default browser, clicking the link launches Chrome in the standard browsing mode. There’s no way to get around this limitation for the time being, as Windows doesn’t allow users to define default apps with special parameters. Unless Google adds such an option in Chrome, the only option is to manually copy each link and paste them in a browsing instance running in Incognito. Source
  21. Google patches ‘evil cursor’ bug in Chrome exploited by tech support scammers A threat group named ‘Partnerstroka’ exploited this bug by replacing the standard mouse cursor (OS 32-by-32 pixels) with 128 or 256 pixels in size. The fix to this ‘evil cursor’ bug is currently live for Google Canary users and is scheduled for the Chrome 75 stable branch soon. Google has patched a bug in Chrome dubbed ‘evil cursor’ that was exploited by the tech support scammers to create an artificial mouse cursor and lock users inside browsers. A security researcher from Malwarebytes, Jerome Segura, who detected this ‘evil cursor’ bug noted that the tech support scammers relied on custom images to replace the system’s standard mouse cursor. The big picture According to Segura, a threat group named ‘Partnerstroka’ exploited this bug by replacing the standard mouse cursor (OS 32-by-32 pixels) with 128 or 256 pixels in size. Even after replacing the standard mouse cursor, it would still appear on the screen, but in the corner of a transparent bounding box. This would trick users into clicking on the area the cursor appears. However, the cursor would click on another area of the screen, preventing users from closing or leaving browser tabs. Why Google took a long time to patch - The security researcher reported this bug to Google last year. However, it took longer for Google to patch this bug. Browsers support custom mouse cursor images for web games, therefore, disabling custom images would impact thousands of gaming sites. Since it is complex to patch the bug without impacting the existing sites, Google developers tested this bug for months and have now come up with a patch. The fix to this bug in Chrome will automatically revert the cursor back to the standard OS graphics when hovering over parts of the Chrome browser interface thereby preventing users from getting locked in browser pages. Worth noting - The fix to this ‘evil cursor’ bug is currently live for Google Canary users and is scheduled for the Chrome 75 stable branch soon. Source
  22. How to Try Out Google Chrome’s New Extensions Menu Google Chrome has the largest collection of browser extensions out there, and this is one of the reasons so many developers decide to build browsers based on Chromium. While the engine itself is obviously very advanced, there’s no doubt that the always-increasing number of extensions makes Chromium a very compelling platform for everyone. And obviously, users are the ones to benefit from the plethora of extensions available for Chromium-based browsers, especially as they further enhance the features of the application themselves. Right now, for example, I have no less than 16 extensions, and I use all of them on a daily basis. Needless to say, some are blocked from being displayed in the toolbar simply because adding more icons here would only make the interface more cluttered and their features can run in the background without any problem. This is actually one key issue for users who install tons of extensions in Google Chrome. The more extensions are installed, the bigger the number of icons showing up in the toolbar, so eventually, using the browser becomes an experience that’s not as straightforward as it was in the beginning. Because the number of extensions is growing at a fast pace and users tend to install more and more in Google Chrome, the search giant is apparently working on a way to resolve this and keep the interface of the browser simple and clean. And it all comes down to an extensions menu that would technically group all browser add-ons and thus make the icons on the toolbar redundant. In other words, this menu would come with its very own icon in the toolbar, and clicking it reveals the available extensions, so you no longer need separate icons for each of them. Or at least, not for all. While there are browsers that already feature such an option, Google Chrome is only now getting it, and by the looks of things, the search giant plans to include it in a future update for the browser. The good news is that this extensions menu is already available in the Canary build of Chrome, so you can try it out in advance before the public launch. One thing worth knowing is that this feature could change significantly by the time it gets the go-ahead for the production builds, so just don’t judge it after trying out the existing implementation. First and foremost, you need to head over to the flags screen to enable the feature. To do this, launch Google Chrome and then type: chrome://flags Next, in the flags section, you need to search for the following entry: #extensions-toolbar-menu The faster alternative is to just copy and paste the following link in the address bar of Google Chrome: chrome://flags/#extensions-toolbar-menu The flag is set to the default mode in Google Chrome Canary for now, and this means that it’s disabled. So click the drop-down menu and switch to Enabled. The browser will then prompt for a reboot. The next time you launch Google Chrome, a new icon should show up in the toolbar, and clicking it displays a list of the available extensions. There’s not much you can do right now because the only option is clicking on each extension to launch it. Most likely, Google would further refine the capabilities in the coming weeks, and one option that would make sense for such a menu is a remove button to quickly uninstall a specific extension. It remains to be seen when Google Chrome will come with such an option in the stable build, but right now, it’s better not to hold your breath for it. Source
  23. Google Chrome to Warn Users of Flash Player Retirement Adobe is planning to retire Flash Player in 2020, and the whole world is preparing for this critical moment, including browser developing companies. Google, for instance, has tried to make the transition off Flash Playeras smoothly as possible, and the upcoming release of Chrome 76 will represent a key step in this regard. The browser will disable Flash Player completely, and users who’ll want this feature enabled will have to do the whole thing manually from the settings screen. But the bigger change coming in Google Chrome is a warning that will be displayed when launching the browser, though there’s a chance that Google could further tweak this behavior in the coming weeks. As discovered by 9to5google, a recent Chromium developer discussion provides us with an early look at the warning, which will be shown as an info bar at the top of the screen. “Flash Player will no longer be supported after December 2020,” the notification reads, and a learn more link gets users to more information about this change.Not yet part of CanaryAccording to a Chromium code commit, the warning is already in the works right now, and will be added at a later time together with a feature flag. “Flash: Add in-product warning infobar about impending Flash deprecation. This CL adds the infobar, but doesn't hook it up to anything. That is forthcoming still. It also adds the feature flag,” the commit reads. Needless to say, warning users in advance that Flash Player support is coming to an end certainly makes the transition smoother, especially as this will be a key point in the history of the world wide web. For the time being, the warning isn’t yet implemented in the Canary builds of Google Chrome, but we’ll continue to monitor the progress in this regard and let you know when you can try it out. Source
  24. Every time Google updates its browser, it publishes release notes aimed at enterprises to highlight upcoming additions, substitutions, enhancements and modifications. Here's some of what's coming. geralt (CC0) Fact: Chrome rules. With a massive two-thirds of the world's browser user share - a measurement of browser activity calculated monthly by analytics vendor Net Applications - Google's Chrome has no peer in popularity. So when Chrome speaks, people listen. That holds true for whatever moves Google makes with each browser upgrade - something Computerworld details in the What's in the latest Chrome update? series - and in what it plans to do in the future. With each update, Google publishes a set of release notes aimed at enterprises. In those release notes, the company highlights some of the upcoming additions, substitutions, enhancements and modifications planned for its browser._ In an effort to look ahead at the browser's future, we've collected the most important of the latest items in Chrome's "Coming soon" category. But as Google takes pains to point out, "They might be changed, delayed, or canceled before launching to the Stable channel." You've been warned. Chrome 75: Legacy browser support baked in What Google has called Legacy Browser Support (LBS) has long been part of the search company's arsenal in its battle for enterprise users. Once configured by IT administrators, LBS automatically opens Internet Explorer 11 (IE11) when links clicked within Chrome lead to websites, web services or web apps requiring Microsoft's browser, or more likely, IE's ActiveX controls or Java, neither of which Google's browser supports. LBS was more important in the days when IE ruled the browser roost and Chrome was scratching for every corporate customer. Today, when Chrome lords it over all browsers - last month it accounted for 67% of all browser user share - LBS has lost its luster. Still, Google plans to bring the capability inside the browser. (It's always before required a Chrome add-on.) "Legacy browser support functionality is being incorporated into Chrome browser, and the separate extension will no longer be needed," Google said. However, the add-on will remain in the Chrome Web Store after Chrome 75's release so that organizations running older versions of the browser still have access to LBS. Chrome 75: End to opt-out of site isolation Unveiled in late 2017 within Chrome 63, Site Isolation is a defensive technology that segregates pages from different sites into different processes. Each process runs in a "sandbox" that restricts what the process can do, all as part of a scheme to isolate malware from the browser as a whole and the device's over-arching OS. Site Isolation was enabled in stages until by mid-2018 it was enabled for virtually all Chrome users. At that point, only managed devices were able to opt-out. As of Chrome 75 - currently scheduled to ship June 4 - that will end. "We've resolved the reported issues and starting with Chrome 75, we will remove the ability to opt out of site isolation on desktop using the SitePerProcess or IsolateOrigins policies," Google said. Chrome 76: Flash to be blocked by default Nearly two years ago, Adobe announced that it would finally bury Flash Player - an app that in many ways, made the web - at the end of 2020. Browser makers like Google then detailed how they would end their support for Flash. While Google has limited Flash for years - in late 2016, it was turned off by default and restricted to a handful of sites, including Amazon, Facebook and YouTube - this summer Chrome will institute a complete Flash blockade. With Chrome 76, now slated to ship July 30, Flash will be disabled by default. Individual users will be able to switch back to a default "Ask to use Flash" in settings (until Google ends all support by yanking it from the Chromium project in December 2020), and enterprises will be able to continue controlling Flash usage through the DefaultPluginsSetting,PluginsAllowedForUrls and PluginsBlockedForUrls policies. Chrome ??: Version roll-back Google will add a browser roll-back process for enterprises that want to retreat to an older version of Chrome, the company said in the latest guidance given to IT administrators. The functionality will be available only to customers using Windows' group policies to manage Chrome. "The new ((group)) policy will allow administrators to roll back in conjunction with the existing TargetVersionPrefix ADMX policy," Google stated. Google will name the new group policy RollbackToTargetVersion. The most likely reason for wanting to roll back Chrome to an earlier version would be because the latest browser caused problems, perhaps a mission-critical app compatibility or workflow issue. When roll-back is implemented, Google will recommend that customers turn on the browser sync feature or alternately, Roaming User Profiles, which lets users take bookmarks, passwords, extensions and preferences to multiple PCs. Failing to do that will mean that data synced from later versions won't be usable by older editions, including the one rolled back to an earlier iteration. Not surprisingly, Google warned, "Use this ((roll-back) policy at your own risk." Source: Fast forward: What's coming in future versions of Chrome? (Computerworld - Gregg Keizer)
  25. Google added "Motion and light sensors" permission controls to Chrome Canary recently so that users of the web browser may control the functionality. Browser makers like Mozilla or Google add new functionality to their browsers regularly. New APIs, the Sensor API is just one example, add new functionality that sites and applications may make use of. APIs may expose data to sites and services, and may even give sites control over functionality. Web browsers like Firefox or Chrome support permissions that give users control over these features. Sensor permissions are available in Chrome Canary only right now; the Android version and the desktop version supports the option. Canary is a development version of Google Chrome; it takes months usually before features land in stable versions of the Chrome browser. Google added global and per-site Sensor access controls to the Chrome web browser which users of the web browser may use to control access to the Sensor API in the browser. Access to Sensors is enabled by default. You may disable Sensors globally or on a per-site basis if you prefer that. Here is how you do that: Load chrome://settings/content/sensors in the Chrome address bar. Doing so opens the Sensor permissions in the browser. Toggle "Allow sites to use motion and light sensors" to enable or disable Sensors globally. Sites that you added to the allow or block list are displayed there as well. Tip: You can manage permissions for other APIs and features by loading chrome://settings/content/. Most, e.g Microphone or Camera are set to "ask" which means that Chrome displays a prompt whenever it detects attempts to access these APIs. The option is also available for individual sites. Just activate the icon that Chrome places in front of the web address to get started. Chrome may display a direct option to allow or block motion or light sensors on a specific site. You may also access the Site settings by activating that link. These display all permissions that Chrome supports. Changes that you may to the site permissions are valid only for the selected site. You may use the options to override global permissions, e.g. to allow a feature on a site or to block it. Closing Words The option to block Sensor API access landed in Chrome Canary 75 and Google has not yet revealed when the feature will land in the stable version. Chrome 75 Stable could be that target, a release that is about 2-3 months away. Source: Google adds Sensor permission controls to Chrome (gHacks - Maertin Brinkmann)
×
×
  • Create New...