Support rolls out chrome stable

Author: m | 2025-04-24

Passkey support rolls out to Chrome stable Passkey support rolls out to Chrome stable

Passkey Support Rolls Out To Chrome Stable - Slashdot

Google announced this week that it plans to change its release schedule for new Chrome updates starting in 2023. Just like Microsoft Edge, Google Chrome will remain on a 4-week release cycle, but Google will soon start pushing an early stable new version of its web browser a week earlier to a subset of users on the Stable channel.“By releasing stable to a small percentage of users early, we get a chance to monitor the release before it rolls out to all of our users. If any showstopping issue is discovered, it can be addressed while the impact is relatively small,” the Chrome team explained, adding that the change will have “little impact” on developers.Windows Intelligence In Your InboxSign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift! "*" indicates required fields In practice, Google plans to make Chrome 110 available on the Beta channel on January 12, 2023. The “early Stable version” will then be released to a subset of users on the Stable channel on February 1. Everyone else on the Stable channel will start receiving Chrome 110 on February 7.It doesn’t seem possible to opt out of receiving early stable versions of Chrome if you’re on the Stable channel, but Google emphasized that only a “small percentage” of Chrome users would receive these “early stable” releases. Google Chrome remains the most popular desktop web browser by a pretty wide margin, so let’s hope this new release schedule won’t be too disrupting for users.

RIP Passwords? Passkey support rolls out to Chrome stable

See pull request: #7387The newsGoogle recently announced that they will begin disabling Manifest V2 extensions in pre-stable versions of Chrome (Dev, Canary, and Beta) as early as June 2024, in Chrome 127 and later. Users impacted by the rollout will see Manifest V2 extensions automatically disabled in their browser and will no longer be able to install Manifest V2 extensions from the Chrome Web Store. "We expect it will take at least a month to observe and stabilize the changes in pre-stable before expanding the rollout to stable channel Chrome, where it will also gradually roll out over time."They have announced this already one year ago, but most likely this will actually happen this time.What does this mean for Scratch Addons?We will upload a Manifest V3 version of the extension to the Chrome Web Store before June 2024.As an indirect consequence, our minimum browser requirements will be affected as well. We currently support, to some extent, browsers versions as old as Chrome 80, released in 2020. We will increase the minum requirement to, at least, Chrome 92 (mid-2021). Older browsers won't be able to run the extension, as they don't know what a manifest three extension is, so it's not possible to show a "unsupported browser" screen in those cases.Plans on end-user browser supportThis is the plan I had in mind to keep up with Chrome's requirements.Add the "export settings" and "view settings as file" buttons to the Unsupported Browser page.This will allow users running old browser versions to export their settings before the extension goes away.We will release a typical MV2 update which will increase the minimum browser requirements to match the MV3 requirements.We will not change our minimum browser requirements as we upgrade to MV3. We will do it earlier. As I said, we can't show any screens or buttons to Chrome versions that don't support basic MV3 functionality, so we have to block them from using the extension earlier.Plans on local development and browser supportOur current MV2 extension has a manifest.json file at root which is accepted by both Chrome and Firefox. They both log warnings, but the raw extension folder as uploaded to GitHub is accepted by both.We plan to change the manifest_version of our manifest file to 3, so all local development will use an MV3 extension, both in Chrome and Firefox.This means contributors will need modern Firefox versions that support MV3, as well as

RIP Passwords? Passkey support rolls out to Chrome stable –

Native Client (NaCl) is a new technology by Google which allows you to embed native executable code in web pages to allow deployment of very performant web apps without requiring the install of plugins. Currently, NaCl is only supported in Google Chrome on Windows, Mac OS X and Linux (with Chrome OS support being worked on), but the technology is open source, so it could be ported to other browser platforms in the future.Unity 3.5 offers support to run Unity Web Player content (.unity3d files) using NaCl to allow content to be run without requiring a plugin install in Chrome. This is an early release - it should be stable to use, but it does not yet support all features supported in the Unity Web Player, because NaCl is an evolving platform, and does not support everything we can do in a browser plugin.Building and Testing games on NaClBuilding and testing games on NaCl is very simple. You need to have Google Chrome installed. Simply choose "Web Player" in Build Settings, and tick the "Enable NaCl" checkbox. This will make sure the generated unity3d file can be run on NaCl (by including GLSL ES shaders needed for NaCl, and by disabling dynamic fonts not supported by NaCl), and install the NaCl runtime and a html file to launch the game in NaCl. If you click Build & Run, Unity will install your player as an app in Chrome and launch it automatically.Shipping Games with NaClIn its current state, NaCl is not enabled for generic web pages in Chrome by default. While you can embed a NaCl player into any web page, and direct your users to manually enable NaCl in chrome://flags, the only way to currently ship NaCl games and have them work out of the box is to deploy. Passkey support rolls out to Chrome stable Passkey support rolls out to Chrome stable

RIP Passwords? Passkey support rolls out to Chrome stable BUT

Linux apps can expand your Chromebook’s capabilities and open up all sorts of interesting options — but first, you have to know where to begin.If you think you’d stand to benefit from using a Linux app on your Chrome OS device — or if you just want to explore and see what’s out there — the first step is to see if your Chromebook supports Linux apps in the first place.Linux app support rolled out to Chrome OS’s main stable channel with Chrome OS 69 in September, but certain hardware and software requirements are attached — which means not all devices are eligible. The simplest way to see if your device has Linux app support is to open up the Chrome OS settings (by typing chrome://settings into the address bar of a browser window) and then type Linux into the search box at the top.If you see a section appear with the label “Linux (Beta),” you’re good to go. If not, your device isn’t supported, and you’ll have to upgrade to a newer or more powerful model in order to use Linux software.Read more at ITWorld

[news] RIP Passwords? Passkey support rolls out to Chrome stable

Hi everyone! We've just released Chrome Dev 135 (135.0.7037.2) for Android. It's now available on Google Play.You can see a partial list of the changes in the Git log. For details on new features, check out the Chromium blog, and for details on web platform updates, check here.If you find a new issue, please let us know by filing a bug.Chrome Release TeamGoogle ChromeSource: Google Chrome Releases The Beta channel is being updated to OS version 16181.24.0 (Browser version 134.0.6998.31) for most ChromeOS devices.If you find new issues, please let us know one of the following ways:File a bugVisit our ChromeOS communitiesGeneral: Chromebook Help CommunityBeta Specific: ChromeOS Beta Help CommunityReport an issue or send feedback on ChromeInterested in switching channels? Find out how.Luis MenezesGoogle ChromeOSSource: Google Chrome Releases Hi everyone! We've just released Chrome Beta 134 (134.0.6998.34) for iOS; it'll become available on App Store in the next few days.You can see a partial list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.Chrome Release TeamGoogle ChromeSource: Google Chrome Releases A new LTS-126 version 126.0.6478.265 (Platform Version: 15886.90.0), is being rolled out for most ChromeOS devices. This version includes selected security fixes including:Fixes for CVE-2024-46800, CVE-2024-49861386143468 High CVE-2025-0611 Object corruption in V8Release notes for LTS-126 can be found here Want to know more about Long-term Support? Click hereGiuliana PritchardGoogle ChromeOSSource: Google Chrome Releases The Stable channel has been updated to 134.0.6998.35 for Windows and 134.0.6998.44 for Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log.You can find more details about early Stable releases here.Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.Srinivas SistaGoogle ChromeSource: Google Chrome Releases The Beta channel has been updated to 134.0.6998.35 for Windows and Linux, 134.0.6998.44 for Mac.A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.Chrome Release TeamGoogle ChromeSource: Google

Passkey support rolls out to Chrome stable – Senior Tech Group

Starting in February 2023, Google Chrome will change up its release cycle slightly with a new “early stable” release designed to catch major issues before they hit all users.Announced in a blog post today, Google Chrome v110 will be the first version of the world’s most popular browser to switch to a new release schedule. As it stands today, new versions of Chrome are released first to the “canary” channel before propagating down to the dev, beta, and finally stable release channels, all of which users are able to opt into.Starting with Chrome 110, Google will expand that release schedule to include a new “early stable” release, which pushes the latest version of Chrome to users a week ahead of the full launch. This pushes the stable release of Chrome 110 back to February 7, 2023, instead of the planned February 1.This won’t be a new opt-in release channel but rather a release schedule that will affect those enrolled in the stable update channel. A “small percentage” of general Chrome users will get the update a week early. Our Kyle Bradshaw points out that this is most likely a larger percentage than those who have chosen to enroll in the beta release channel, or it could be that Google is simply targeting a different subset of Chrome’s user base. For the first release, Google notes that the schedule will be as follows:Beta: January 12, 2023Early Stable: February 1, 2023Stable: February 7, 2023Google explains that the reasoning for this tweak to. Passkey support rolls out to Chrome stable