Google Chrome Metro app due soon.


Recommended Posts

Back in March, we began work on a Metro-style enabled desktop browser, a version of Chrome that will run in both the Metro and desktop environments of Windows 8 on x86. (Chrome won?t run in WinRT, i.e. Windows 8 on ARM processors, as Microsoft is not allowing browsers other than Internet Explorer on the platform.) If you?re running the Release Preview of Windows 8, you?ll be able to try Chrome in Metro mode in the next Chrome Dev channel release by setting it as your default browser.

chrome_in_metro.png

The initial releases of Chrome in Metro mode will include integration with the basic Windows 8 system functionality, such as charms and snap view. Over the next few months, we?ll be smoothing out the UI on Metro and improving touch support, so please feel free to file bugs. We?re committed to bringing the speed, simplicity, and security of Chrome into Windows 8, and we look forward to working with you on it.

Source - http://blog.chromium.org/2012/06/try-chrome-in-metro-mode.html

I can't wait for this, and yes, that screenshot is the metro-style mode from the lack of settings among other things.

Link to comment
https://www.neowin.net/forum/topic/1082655-google-chrome-metro-app-due-soon/
Share on other sites

They will have to work on those controls to make them touch friendly in size.

They're doing that later on. The harder part is making Chrome work properly with all the Start Screen like Charms and snap view. Adding some bigger icons and including a switch to make some things bigger isn't exactly a challenge.

I'm not normally one to say this but I hope Microsoft get sued for not allowing non-IE browsers on the arm version of Windows 8. Although I'd never buy a tablet or anything else powered by Metro, I'd hate to be stuck with only IE on any platform.

I'm not normally one to say this but I hope Microsoft get sued for not allowing non-IE browsers on the arm version of Windows 8. Although I'd never buy a tablet or anything else powered by Metro, I'd hate to be stuck with only IE on any platform.

*sigh* Who said they don't allow other browsers on the ARM version? Any metro browser will run on it just as it does on x86. What they don't allow are desktop apps on the ARM version.

I'm not normally one to say this but I hope Microsoft get sued for not allowing non-IE browsers on the arm version of Windows 8. Although I'd never buy a tablet or anything else powered by Metro, I'd hate to be stuck with only IE on any platform.

I thought they only disallowed browsers on ARM for the desktop, not metro. There is nothing stopping them in that case from making a full metro app that doesn't depend on an installed version of Chrome for the desktop.

They will have to work on those controls to make them touch friendly in size.

From looking in about:flags on Chromium builds, all that'll happen is like menus and that have bigger clicking space. Navigation buttons are fine for touch.

*sigh* Who said they don't allow other browsers on the ARM version? Any metro browser will run on it just as it does on x86. What they don't allow are desktop apps on the ARM version.

So their browser, mysteriously is available in the desktop but nobody else's is. Still sounds like an arbitrary limitation to me.

I thought they only disallowed browsers on ARM for the desktop, not metro. There is nothing stopping them in that case from making a full metro app that doesn't depend on an installed version of Chrome for the desktop.

Again, a sign of the trend that they're trying to force everyone to go Metro

So their browser, mysteriously is available in the desktop but nobody else's is. Still sounds like an arbitrary limitation to me.

Again, a sign of the trend that they're trying to force everyone to go Metro

I believe they stated a valid reason for disallowing browsers on the desktop for Windows RT. Cannot conjure it up right this second though.

I personally have no issue with them pushing towards Metro, if I was a developer of something like this I'd do the exact same thing and push people towards it.

So their browser, mysteriously is available in the desktop but nobody else's is. Still sounds like an arbitrary limitation to me.

Again, a sign of the trend that they're trying to force everyone to go Metro

There's nothing suspect about it, the simple fact, and technical fact is that the desktop on ARM isn't the same desktop, x86 apps won't run and MS isn't going to customize it or build in compatibility for it, the only apps will be Office and while IE10 for the desktop is there (for now, could change) you're not going to go into the desktop to use the desktop version that's a pain to use with touch on a touch tablet.

If MS allows desktop apps on the ARM version it'll only make a mess of things. The last thing we need, or anyone else, is for people to think they can install any x86 desktop app on the ARM version then turn around and bitch because it doesn't install or just crashes when they try to run it.

I believe they stated a valid reason for disallowing browsers on the desktop for Windows RT. Cannot conjure it up right this second though.

I personally have no issue with them pushing towards Metro, if I was a developer of something like this I'd do the exact same thing and push people towards it.

If IE can be ran on it, their reasons regardless of how well they have sucked you in are pure bunk.

There's nothing suspect about it, the simple fact, and technical fact is that the desktop on ARM isn't the same desktop, x86 apps won't run and MS isn't going to customize it or build in compatibility for it, the only apps will be Office and while IE10 for the desktop is there (for now, could change) you're not going to go into the desktop to use the desktop version that's a pain to use with touch on a touch tablet.

If MS allows desktop apps on the ARM version it'll only make a mess of things. The last thing we need, or anyone else, is for people to think they can install any x86 desktop app on the ARM version then turn around and bitch because it doesn't install or just crashes when they try to run it.

No, it is exactly the same desktop, just compiled to run on a different architecture. And hell it's not as if software vendors could *gasp* just do the same thing, now, is it?

No, it is exactly the same desktop, just compiled to run on a different architecture. And hell it's not as if software vendors could *gasp* just do the same thing, now, is it?

Just because it looks the same doesn't make it the same, each ARM version of Windows RT, and this has been stated officially, has been custom coded to run on specific ARM SoCs since they're not all exactly the same. You really think it's just a matter of recompiling your x86 app to ARM and it'll magically just run?

I really do hope the design for the Metro experience ends up being more than just larger icons and more spacing. I would highly dislike the current Chrome design when in the Metro experience.

Fully agree, it would seem stupidly out of place.

Just because it looks the same doesn't make it the same, each ARM version of Windows RT, and this has been stated officially, has been custom coded to run on specific ARM SoCs since they're not all exactly the same. You really think it's just a matter of recompiling your x86 app to ARM and it'll magically just run?

Strange, it seems to work for Linux and Android... save perhaps for a bit of custom kernel code tailored to specific device requirements.

I seriously doubt Chrome can magically catch up to IE10 speed.

Seeing as it's already ahead in every test apart from Javascript I'm interested to see what exactly you base that inference on.

Seeing as it's already ahead in every test apart from Javascript I'm interested to see what exactly you base that inference on.

Real world performance with full D2D HWA, scroll smoothness and responsiveness.

Strange, it seems to work for Linux and Android... save perhaps for a bit of custom kernel code tailored to specific device requirements.

Funny, and all this time I thought Android apps were written in Java.

Strange, it seems to work for Linux and Android... save perhaps for a bit of custom kernel code tailored to specific device requirements.

Which is why Android's performance is a joke and nobody wants Android-based tablets. Microsoft have imposed deliberate restrictions to ensure the stability and performance of WoA so they don't end up in the same mess as Google have.

If you want a tablet that allows you to install whatever you want to the desktop then just buy an x86-based tablet.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!