Archive for the ‘Chromium’ Category

Microsoft publishes first Edge for macOS preview, promises to make it truly “Mac-like”

May 20th, 2019
Microsoft publishes first Edge for macOS preview, promises to make it truly “Mac-like”

Enlarge (credit: Microsoft)

One of the most important ways that Microsoft wants to make the new Chromium-based Edge different from the current EdgeHTML-based Edge is in its support for other platforms. The original Edge was, for no good reason, tied to Windows 10, meaning that Web developers on platforms such as Windows 7 or macOS had no way of testing how their pages looked, short of firing up a Windows 10 virtual machine.

The new browser is, in contrast, a cross-platform affair. The first preview builds were published for Windows 10, with versions for Windows 7, 8, and 8.1 promised soon; today, these are joined by builds for macOS.

The macOS version resembles the Windows 10 builds that we've seen so far, but it isn't identical. Microsoft wants to be a good citizen on macOS by producing not just an application that fits the platform's standards—using the right fonts, icons, spacing, and so on—but which also adapts to Apple's unique hardware. To that end, the company is working on support for the Touch Bar found on some of Apple's portable systems, using it for media control, tab switching, or access to bookmarks. Microsoft will also work to ensure that Edge's support as a Progressive Web App host properly adopts macOS behaviors with regard to interaction with the Dock, app switcher, and Spotlight.

Read 2 remaining paragraphs | Comments

Posted in browser, Chromium, EDGE, MacOS, microsoft, Tech | Comments (0)

Microsoft’s plan for Edge: Integrated IE compatibility, better privacy

May 6th, 2019

Microsoft has outlined its plans for the next stage of development for the new Chromium-based Edge browser, and those plans include a trio of new features.

The first is a big nod to enterprise customers: a built-in Internet Explorer mode. Chrome has a number of extensions that accomplish much the same thing—they create a new tab in the browser and use the Internet Explorer 11 engine, rather than the Chrome engine, to draw that tab. For Edge, this capability will be built in.

Enterprises can already create a compatibility list, the Enterprise Mode Site List, which the current Edge browser uses to know which (internal, line-of-business) sites should be shown in Internet Explorer 11. The new Edge will use this same list to determine when to use Internet Explorer.

Read 3 remaining paragraphs | Comments

Posted in browsers, build 2019, chrome, Chromium, EDGE, microsoft, Open Source, Tech | Comments (0)

Windows 10’s “Sets” tabbed windows will never see the light of day

April 23rd, 2019
Microsoft's inspiration, evidently.

Enlarge / Microsoft's inspiration, evidently. (credit: Jerry / Flickr)

For two periods last year, those using preview builds of Windows 10 could access to a feature called Sets: a tabbed interface that was eventually to allow tabs to be put in the titlebar of just about any window. These tabs would allow both multiple copies of the same application to be combined—a tabbed Explorer or Command Prompt, say—and multiple disparate windows to be grouped—combining, say, a browser window containing research with the Word window. However, both times the feature was enabled only for a few weeks, so Microsoft could gather data, before disabling it. Sets aren't in the Windows 10 May 2019 update.

It seems now that Sets are unlikely to ever materialize. Rich Turner, who oversees Microsoft's revamping of the Windows command-line infrastructure and the Windows Subsystem for Linux tweeted that the interface "is no more." Having everything tabbed everywhere isn't going to happen. Adding tabs specifically for command-line windows is, however, "high on [Microsoft's] to do list."

There was initially some confusion that the tweet might have meant that some other system-wide approach to tabs was going to be used. But Turner clarified today that the command-line tabs will be purpose-built for command-line windows, not a general feature for the entire operating system.

Read 4 remaining paragraphs | Comments

Posted in browser, Chromium, EDGE, microsoft, Open Source, sets, tabs, Tech, user interface, Windows | Comments (0)

Microsoft Releases First Preview Builds of Chromium-based Edge Browser

April 8th, 2019
Microsoft today finally released the first new reborn version of its Edge browser that the company rebuilds from scratch using Chromium engine, the same open-source web rendering engine that powers Google's Chrome browser. However, the Chromium-based Edge browser builds haven't yet entered the stable or even the beta release; instead, Microsoft has released two testing-purpose preview builds

Posted in browser, browser security, Chromium, Download Browser, Google Chrome, Microsoft Edge browser, web browser | Comments (0)

Hands-on: First public previews of Chromium-based Edge are now out

April 8th, 2019
There's really no difference between how the Ars front page looks in Edge and Chrome.

Enlarge / There's really no difference between how the Ars front page looks in Edge and Chrome.

Microsoft's switch to using the Chromium engine to power its Edge browser was announced in December last year, and the first public preview build is out now. Canary builds, updated daily, and Dev builds, updated weekly, are available for Windows 10. Versions for other operating systems and a beta that's updated every six weeks are promised to be coming soon.

Chromium is the open source browser project run by Google. It includes the Blink rendering engine (Google's fork of Apple's WebKit), V8 JavaScript engine, Google's software-based sandboxing, and the browser user interface. Google builds on Chromium for its Chrome browser, and a number of third-party browsers, including Opera, Vivaldi, and Brave, also use Chromium.

As a result, every Chromium browser offers more or less the same performance and Web compatibility. Indeed, this is a big part of why Microsoft made the switch: the company had grown tired of updating its own EdgeHTML engine to ensure it behaved identically to Chrome and is now offering Chrome-equivalent behavior in the most direct way possible. I've been using a version 74 build (which is a little out of date at this point) for the last week, and I have yet to see any difference between Edge and Chromium Dev when it comes to displaying Web pages. In principle, a page could treat Edge differently (it reports its identity as a rather ugly "Edg/74.1.96.14"; I'm presuming the misspelling is an attempt to ensure it isn't identified as a variation of the current Edge browser), but in general there's little reason to do so.

Read 5 remaining paragraphs | Comments

Posted in browsers, Chromium, development, EDGE, microsoft, Open Source, Tech, the web, Windows | Comments (0)

Edge-on-Chromium approaches; build leaks, extensions page already live

March 25th, 2019

The Edge Insider extension.

The Edge Insider extension. (credit: Microsoft)

Microsoft's first public release of a Chromium-based version of its Edge browser is fast approaching. Microsoft has published an early version of its extension market for the new browser, and the Windows Store includes a new extension for Edge-on-Chromium. On top of all this, a build of the browser has leaked.

The new build confirms much of what we've seen before: the browser is a minimally changed rebranded version of Chrome, replacing integration with Google's accounts with integration with Microsoft's accounts. This integration is still at an early stage; bookmarks can be synced between systems, but history, passwords, open tabs, autocomplete information, and open tabs don't yet sync.

Google has multiple release channels for Chrome; beyond the Stable channel, there's a Beta channel previewing the next release, the Dev channel previewing the release after that, and the Canary channel, which provides nightly builds. Microsoft's new extension for Edge Insider appears to offer easy switching between channels, announcements, known issues, and asking users for focused testing on particular areas.

Read 4 remaining paragraphs | Comments

Posted in browsers, chrome, Chromium, EDGE, google, microsoft, Open Source, Tech, Web, Windows | Comments (0)

Google turbo-charging the back button with Chrome’s new “back/forward cache”

February 28th, 2019
Now that's some shiny chrome.

Enlarge / Now that's some shiny chrome. (credit: Marc Ellis / Flickr)

Google is developing a new cache for Chrome (via CNET)that should make some page loads extremely fast. The only catch? They'll have to be pages you've already seen and are revisiting after hitting the browser's back button.

Chrome already caches the files that make up a page, so revisiting a page in most circumstances shouldn't force the browser to retrieve the images, JavaScripts, and CSS that are used to build the page. But currently, the browser has to re-parse the HTML and re-build the page's programmatic representation, uncompress the images, re-execute all the JavaScript, reapply all the stylesheets, and so on. It's just the networking step that gets skipped.

The new bfcache (for "back/forward cache") changes that: it lets the browser capture the entire state of a running page—including scripts that are in the middle of execution, the rendered images, and even the scroll position—and reload that state later. With bfcache, rather than having to reload the page from scratch, the page will look as if it was paused when you click a link to a new page and subsequently resumed when you hit back.

Read 4 remaining paragraphs | Comments

Posted in browsers, chrome, Chromium, development, google, Tech | Comments (0)

Google partially backtracks on Chrome changes that would break ad blockers

February 18th, 2019

Google has said that it will revise the proposed changes to Chrome's extension API that would have broken or reduced the functionality of a wide range of ad-blocking extensions, to ensure that the current variety of content-blocking extensions is preserved. The initial plans generated a wide backlash from both the developers and users of those extensions, but Google maintains that "It is not, nor has it ever been, our goal to prevent or break content blocking" [emphasis Google's] and says that it will work to update its proposal to address the capability gaps and pain points.

The advertising company is planning an overhaul of its extension interface to, among other things, increase user privacy, make it harder for extensions to perform malicious actions, and make the browser's performance more consistent. Together, this work is documented as Manifest V3.

One of these changes in particular had grave consequences for ad blockers. Currently, ad blockers make extensive use of an API named webRequest. This API allows extensions to examine every single network request made by a page and either modify it (to, for example, redirect it to a different address or add or remove cookies), block it altogether, or allow it to continue unhindered. This has both a substantial privacy impact (an extension can see and steal your cookies and hence masquerade as you) and, Google said, some performance impact, as every single network request (of which there may be dozens in a single page) has to wait for the extension to perform its analysis.

Read 7 remaining paragraphs | Comments

Posted in ad blockers, chrome, Chromium, development, google, Open Source, Tech, Web | Comments (0)

With experimental “Never slow mode,” Chrome tries to stop Web devs making it slow

February 6th, 2019
The word SLOW has been painted on a street for the benefit of drivers.

Enlarge / Google wants less of this. (credit: Vegansoldier / Flickr)

Since Chrome's very first release, performance has been one of Google's top priorities. But Google is against a competing force: Web developers. The Web of today is a more-complex, bandwidth-intensive place than it was when Chrome was first released, which means that—although Internet connections and the browser itself are faster than they've ever been—slow pages remain an everyday occurrence.

Google engineers have been developing "Never Slow Mode" in a bid to counter this. Spotted at Chrome Story (via ZDNet), the new mode places tight limitations on Web content in an effort to make its performance more robust and predictable.

The exact design and rationale of Never Slow Mode aren't public—the changelog for the feature mentions a design document but says it's currently Google-internal. But taken together, that design and rationale will ensure that the browser's main thread never has to do too much work and will never get too delayed. They will also ensure that only limited amounts of data are pulled down over the network. This should make the browser more responsive to user input, lighter on the network, and a bit less of a memory hog than it would otherwise be.

Read 4 remaining paragraphs | Comments

Posted in browsers, chrome, Chromium, google, HTML, Open Source, Tech, Web | Comments (0)

Post-mortem: Tying Edge to Windows 10 was a fatal error

December 6th, 2018
Post-mortem: Tying Edge to Windows 10 was a fatal error

Enlarge (credit: @AndreTelevise)

As reported earlier this week, Microsoft is going to use Google's Blink rendering engine and V8 JavaScript engine in its Edge browser, largely ending development of its own EdgeHTML rendering engine and Chakra JavaScript engine. This means that Microsoft will be using code from—and making contributions to—the Chromium open source project.

The company's browser will still be named Edge and should retain the current look and feel. The decision to switch was motivated primarily by compatibility problems: Web developers increasingly test their pages exclusively in Chrome, which has put Edge at a significant disadvantage. Microsoft's engineers have found that problematic pages could often be made Edge compatible with only very minor alterations, but because Web devs aren't using Edge at all, they don't even know that they need to change anything.

The story is, however, a little more complex. The initial version of Edge that shipped with the first version of Windows 10 was rudimentary, to say the least. It was the bare bones of a browser, but with extremely limited capabilities around things like tab management and password management, no extension model, and generally lacking in the creature comforts that represent the difference between a bare rendering engine and an actual usable browser. It also had stability issues; crashes and hangs were not uncommon.

Read 12 remaining paragraphs | Comments

Posted in Blink, chrome, Chromium, development, EDGE, google, JavaScript, microsoft, Open Source, Tech, WebKit | Comments (0)