Microsoft’s Chromium-Based Edge Browser Looks Just Like Chrome

Last December, Microsoft announced that it has embraced Google’s Chromium open source project for Edge development on the desktop, a move that shocked many. We now have some leaked screenshots of the browser in its current state, and they appear to show a browser resembling Google Chrome. Neowin reports: A lot of the design language and icons have remained similar to what they were like before, but there are definitely many changes that will be familiar to Chrome users. For one, the options to see all your tabs and to set aside the currently open tabs have been removed compared to the current version of Edge. To the right of the address bar, you’ll be able to find your extensions, as well as your profile picture similar to what Chrome looks like. Bing is integrated into the browser — as you’d expect of a Microsoft-made browser — and the New


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/S2nRyGTJ5As/microsofts-chromium-based-edge-browser-looks-just-like-chrome

Original article

Chrome API Update Will Kill a Bunch of Other Extensions, Not Just Ad Blockers

An anonymous reader writes: A planned update to one of the Google Chrome extensions APIs would kill much more than a few ad blockers, ZDNet has learned, including browser extensions for antivirus products, parental control enforcement, phishing detection, and various privacy-enhancing services. Developers for extensions published by F-Secure, NoScript, Amnesty International, and Ermes Cyber Security, among others, made their concerns public today after news broke this week that Google was considering the API change. Furthermore, efforts to port NoScript from Firefox to Chrome are also impacted, according to the plugin’s author, who says the new API update all but cripples the NoScript for Chrome port.

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/_XsTC8KKs8c/chrome-api-update-will-kill-a-bunch-of-other-extensions-not-just-ad-blockers

Original article

How to use picture-in-picture mode in Chrome 70

The Chrome web browser was starting to get some bad press after problems with extensions and then concerns over automatic sign-ins. Google listened to the complaints and promised to do something about it — the result is Chrome 70. But Chrome 70 is about more than just security and privacy changes. Google has also used this released to introduce a handful of new features. One of the best is picture-in-picture mode (PiP) which lets you keep watching a video in an overlay while you continue to browse other sites. Here’s how to use it. See also: Chrome 70 introduces more… [Continue Reading]


Original URL: https://betanews.com/2018/10/20/chrome-picture-in-picture/

Original article

Google Slammed Over Chrome Change That Strips ‘www’ From Domain URLs

An anonymous reader quotes ITWire:
Google’s move to strip out the www in domains typed into the address bar, beginning with version 69 of its Chrome browser, has drawn an enormous amount of criticism from developers who see the move as a bid to cement the company’s dominance of the Web. The criticism comes a few days after Chrome’s engineering manager Adrienne Porter Felt told the American website Wired that URLs need to be got rid of altogether. The change in Chrome version 69 means that if one types in a domain such as www.itwire.com into the browser search bar, the www portion is stripped out in the address bar when the page is displayed.
When asked about this change in a long discussion thread on a mailing list, a Google staffer wrote: “www is now considered a ‘trivial’ subdomain, and hiding trivial subdomains can be disabled in flags (will also


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/L5PquTjuPcY/google-slammed-over-chrome-change-that-strips-www-from-domain-urls

Original article

Chrome 69 Arrives With Revamped Design, More Powerful Omnibox, and Better Password Manager

An anonymous reader writes: Google today launched Chrome 69 for Windows, Mac, and Linux, Android, and iOS, just a few days after the browser’s 10-year anniversary. The release includes a new design, more powerful omnibox, updated password manager, more accurate autofill, plenty of developer-specific changes, and a slew of security improvements. You can update to the latest version now using Chrome’s built-in updater, download it directly from google.com/chrome, or grab it from Google Play and Apple’s App Store. Further reading: As Chrome turns 10, Google bets on AI and AR, and Google wants to kill the URL.

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/91ceGk1e4kw/chrome-69-arrives-with-revamped-design-more-powerful-omnibox-and-better-password-manager

Original article

Chrome has a secret Material Design mode — here’s how to enable it

With the launch of Chrome 68 a few days ago, Google changed the way it handled non-HTTPS websites. But the browser update also hides a secret — a Material Design mode that you can enable by tinkering with the relevant hidden settings. The new look is currently available on the desktop and in the iOS version of Chrome, and it gives the browser a much cleaner, fresher look and a bit of a UI rejig. See also: Brace yourself for a slew of security warnings from Chrome Chrome will stop highlighting HTTPS sites as secure Chrome’s RAM usage is higher… [Continue Reading]


Original URL: https://betanews.com/2018/07/26/chrome-secret-material-design/

Original article

Google Chrome 67 Released for Windows, Mac, and Linux

An anonymous reader shares a report: Google released earlier today Chrome 67, the latest stable release of its web browser. According to changelogs released with Chrome 67, this version adds support for a Generic Sensors API, improves AR and VR experiences, and deprecates the HTTP-Based Public Key Pinning (HPKP) security feature. Probably the biggest change in Chrome 67 is the addition of the Generic Sensors API. As the name implies, this is an API that exposes data from device sensors to public websites. The new API is based on the Generic Sensor W3C standard. This API is meant primarily for mobile use, and in its current version, websites can use Chrome’s Generic Sensors API to access data from a device’s accelerometer, gyroscope, orientation and motion sensors. Another API that shipped with Chrome is the WebXR Device API. Developers can use this API to build virtual and augmented reality experiences on


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/HoeAfFP1oIY/google-chrome-67-released-for-windows-mac-and-linux

Original article

Google Chrome To Remove ‘Secure’ Indicator From HTTPS Pages in September

Google announced Thursday it plans to drop the “Secure” indicator from the Chrome URL address bar — starting with Chrome v68, set for release in July — and only show a lock icon when the user is navigating to an HTTPS-secured website. From a report: The move is scheduled to take effect with the release of Chrome 69, scheduled for September, this year. Emily Schechter, Product Manager for Chrome Security, said the company is now comfortable making this move as a large chunk of Chrome’s traffic is now via HTTPS. Since most traffic is HTTPS anyway, it’s not necessary to draw the user’s attention to the “Secure” indicator anymore.

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/kt0HU48kvYI/google-chrome-to-remove-secure-indicator-from-https-pages-in-september

Original article

Starting Today, Google Chrome Will Show Warnings for Non-Logged SSL Certificates

Starting today, Google Chrome will show a full-page warning whenever users are accessing an HTTPS website that’s using an SSL certificate that has not been logged in a public Certificate Transparency (CT) log. From a report: By doing so, Chrome becomes the first browser to implement support for the Certificate Transparency Log Policy. Other browser makers have also agreed to support this mechanism in the future, albeit they have not provided more details. This new policy was first proposed by Google engineers in 2016, and was scheduled to enter into effect in October 2017, but was later delayed for 2018.

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/CqCv19vOG0U/starting-today-google-chrome-will-show-warnings-for-non-logged-ssl-certificates

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: