Recommended Posts

I thought why not also a "next" thread for Chrome?

Stay informed:

Google Chrome Blog

Chromium Blog

Chromium Homepage

Google Chrome Releases

Downloads:

Google Chrome Final

Google Chrome Beta

Google Chrome Dev

Chromium Builds (not recommended)

Other Chrome threads:

Google Chrome 22.0.xxxx.yy

We can collect Chrome news here.

Link to comment
https://www.neowin.net/forum/topic/1094641-meet-the-browser-chrome-next/
Share on other sites

I can not edit my post anymore :(

PM a mod and they will edit it for you.

P.S. It's about time you Chrome junkies finally got some common sense and create a single thread for all of your releases. Firefox has had their own for more than a year.

I just wonder if Google will ever try a new GUI... those tabs are... :no:

What's supposedly "wrong" with the tabs in Chrome?

Absolutely nothing. Google gets the concept of not messing around with GUI and just focusing on what really matters: performance and features. If only Mozilla could take a hint, they could catch up on those areas.

I just don't like them aesthetically. I would like something more minimal and (at least apparently) more OS integrated.

I disagree. The tabs in Chrome are very simple, minimalist and efficient. I really don't like the angular tabs seen in other browsers and Mozilla has clearly come to the same conclusion as they're looking to change to a style similar to Chrome's tabs. Google hit on a very good UI from the get-go and it's one of the few browsers to not undergo considerable visual changes.

Don't see that much of a difference

I like the curves and how everything is integrated in the title bar. The GUI in Australis, for me, it's more elegant while in Chrome it's... blank, for a lack of a better word.

Firefox-Australis.jpg

I'm using Google Chrome v22.0.1215.3 dev-m and I don't have that. Come on Google update the branch!!

I am on Chromium 22.0.1221.0 (Build 148901)..

Also in Chrome 22, Google enabled hardware accelerated video decode.

Lets see when Aura UI of Chrome OS lands on desktop..

Dev Channel Update

The Dev channel has been updated to 22.0.1221.0 for Windows and Mac. This update has an updated version of V8 (3.12.16.0) along with other improvements. A complete log of what changed can be found in the svn revision log. Instructions and download links for our different release channels are available on the Chromium wiki. If you find what you think is a new bug, please file it in our issue tracker.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

The new site information pop-up from Zlip792's screenshot is in this build.

I'm running the latest Canary build (dev build?) along with the latest Chromium build as well. Anything Flash eventually crashes on me in Canary, but not Chromium. Actually thinking about going back to the beta channel until the Flash issue is resolved, as it is rather annoying obviously. I've reported it so hopefully other people are having the same issue and Google can work on it at some point :)

I'm running the latest Canary build (dev build?) along with the latest Chromium build as well. Anything Flash eventually crashes on me in Canary, but not Chromium. Actually thinking about going back to the beta channel until the Flash issue is resolved, as it is rather annoying obviously. I've reported it so hopefully other people are having the same issue and Google can work on it at some point :)

did they fix the flickering issue in the dev build? I switched to stable because of that.

will switch once they fix it.

Its on all page and reopening the browser fix it sometime but its a hit or miss.

Its a huge triangle flicker on the top of the page. happens to most of the web pages.

here is the screenshot from chrome issue tracker http://code.google.c...etail?id=136334

attachment?aid=1363340000000&name=example+1.png&token=WYlchE3XnAROkWcPKkPAXpFwijg%3A1343752389574&inline=1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
    • wow. that color finally comes to Surface Pro. was always a little jelly when a friend had the sandstone Surface Laptop. I wonder how different this dune is from the sandstone. I'll be getting the dune version. always thought black and platinum were a little boring. I'll still have access to my blue Surface Pro 11 as it'll be a hand-me-down.
    • Looks a very subjective aren't they!? I like its simple design. I love the way Apple designs their products with function over form, minimalization, and simplicity over cluttered complex designs. Many, not all, of their products follow this trend, and the device becomes a tool rather than dominating the space. I do not however like their OS. I have never bought a Apple product, and while I'd consider the Neo for my wife, I am hoping there are better alternatives out there when her failing MacBook Pro 2017 finally stops. Fischer-Price is famously plastic, garish, and poorly made. Basically you're describing the Window Laptops the Neo competes against! This is how product design should be, and what Apple have often followed in recent years: https://tenprinciples.design/
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      58
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!