chrome enable experimental web platform features

How to Enable Experimental Web Platform Features in Chrome Browser

Enable Experimental Web Platform Features!

As of now, there are plenty of web browsers available for Windows 10. However, out of all those, it was Google Chrome that stands out from the crowd. Compared to other web browsers for desktop, Chrome offers more features and options.

Google also has a beta version of the Chrome web browser that allows users to test upcoming features. Chrome beta is meant for testing, and it has lots of experimental features. However, to test out the experimental features, one needs to enable certain flags.

If the features perform well after months of testing, they were pushed to the stable version of Google Chrome. Google Chrome users can try such features by enabling the ‘Experimental Web Platform Features.’

The Experimental Web Platform Features in Google Chrome enables experimental web platform features that are currently in development for those who don’t know. You can enable this flag on Chrome for Android, Mac, Windows, Linux, Chrome OS, and Linux.

Also Read:  How to Create Custom Google Chrome Address Bar Actions

Steps to Enable Experimental Web Platform Features in Chrome Browser

This article will share a detailed guide on how to enable Experimental web platform features in the Google Chrome web browser.

Step 1. First of all, open your Google Chrome web browser and type in ‘Chrome://flags’

Step 2. This will open the Chrome Experiments page .

Step 3. On the Search box, type in ‘Experimental Web Platform Features.’

Step 4. Now set the Experimental Web Platform features to ‘Enabled’ from the drop-down menu.

Step 5. Once enabled, click on the ‘Relaunch’ button to restart the web browser.

That’s it! You are done. Now your Google Chrome browser will have the features that are in development. If some features were enabled by default, then you don’t need to make any changes. However, some features may require enabling certain flags.

Note: The experimental features are not available in the stable version for a reason. Enabling feature experimental features might impact your browser’s performance. So, make sure to enable Chrome flags at your own risk.

So, this article is all about how to enable Google Chrome flags to test the beta features. I hope this article helped you! Please share it with your friends also. If you have any doubts related to this, let us know in the comment box below.

RECOMMENDED ARTICLES RELATED ARTICLES

Windows Update Error 0x800703e6? Here’s how you can fix it

Download uTorrent Offline Installer Latest Version (Windows, Mac & Linux)

How to Change WhatsApp 24-hour Time Format to 12-hour

Leave a reply cancel reply.

Save my name, email, and website in this browser for the next time I comment.

6 Best BitSearch Alternatives in 2024 (Torrent Search Engines)

Apple introduces ‘clean up’ feature in ios 18.1 beta 3, 6 best telegram client apps for windows.

• Privacy Policy

• Help Center
• Google Chrome
• Privacy Policy
• Terms of Service
• Submit feedback

Test experimental features in Chrome

You can test features before they’re added to Chrome and give feedback.

Turn features on or off

To use experimental features, download Chrome Beta .

• Open Chrome.

• Restart your browser.

Give feedback on features

If you test any features, you can give feedback about:

• Your experience with the feature
• Issues or problems
• Suggested improvements

To give feedback:

• Next to the feature’s name and description, select Send Feedback .

To send general feedback about Chrome, learn more about how to report an issue or send feedback in Chrome .

Related resources

• Customize Chrome themes with AI
• Get started with Tab organizer in Chrome
• Try Experiments in Search Labs

Was this helpful?

Need more help, try these next steps:.

• Mobile Computing

• Good to know
• VPN for streaming
• VPNs for gaming
• Privacy news
• VPN reviews
• Windows 11 News
• Windows 11 Help
• Windows tips
• Windows Update
• Data Recovery
• File Sharing
• Microsoft Office
• Firefox add-ons
• Chrome Extensions
• Internet Explorer
• Microsoft Edge
• Google Maps
• Google Android
• Thunderbird
• Crypto & Blockchain
• Development
• Music and Video

How to use Google Chrome Flags to enable experimental features

Google Chrome and other Chromium-based browsers work out of the box for the most part. All versions of Google Chrome come with support for "Chrome flags", which unlocks a treasure trove of features, many of which are considered beta or experimental.

Google uses different Chrome editions for development purposes, including Chrome Canary and Beta. Some features are introduced as flags, and users need to enable them to make them work in the browser. While it is often not recommended to do so, especially in work environments, it may sometimes unlock useful features that would not be available for weeks or months otherwise.

Many features of Chrome's flag page are integrated natively in the browser at one point in development, but it may also happen that some are removed without further notice.

How to access Chrome Flags

All users may access experimental flags in Chrome. All that is required for that is to type chrome://flags in the browser to get started.

Google Chrome displays a warning at the top and the list of flags below that on the page. The list begins with flags that are user-enabled, and then the remaining flags. The unavailable tab lists flags that are not available, e.g. because they are not supported on a platform or setup.

Each flag is listed with its name, a short description, platform availability, and status. There is also a handy link to jump to that flag right away in the browser.

Title and description are often enough to figure out what a particular flag does. Sometimes, you may need to run a search for the name of a feature to find out more before changing its status.

An example: If you load chrome://flags/#enable-tab-search in Chrome, the Tab Search experiment is displayed. You may select the box on the right to change the status of the flag to Enabled or Disabled. Changes require a restart of the browser before they take effect. Chrome will display a relaunch button

You may encounter different statuses when you work with the chrome://flags page. The most common ones are:

• Default -- this is the default value as set by Google. Its value can be Enabled or Disabled, or it may have another value.
• Enabled -- the experimental Chrome flag is enabled.
• Disabled -- the flag is disabled in the browser.

Closing Words

Chrome Flags opens a world of configuration options. You may use them to enable features that are not ready for inclusion in Chrome Stable, or disable features that Google is testing currently.

Ultimately, it is not as great of a configuration tool as Firefox's about:config page, but it gives Chrome users temporary control over some features of the browser.

All other Chromium-based browsers, including Microsoft Edge, Brave, Opera and Vivaldi, support flags as well. You may open them using  a different address, e.g. edge://flags instead of chrome://flags in Microsoft Edge, but the available experiments are mostly the same.

Now You : do you tweak flags in your browser?

Related content

Google Chrome: security update fixes 38 issues, including one that is actively exploited

Google is killing uBlock Origin in Chrome, but this trick lets you keep it for another year

The end of Patreon? Google is implementing micro-payments into Chrome

About Chrome's "These extensions may soon no longer be supported" message

Google gives up: third-party cookies won't go away after all in Chrome

Google Chrome will soon throw security warnings at you that you cannot ignore

Developers need to get this page in order! Too many flags have accumulated there … IMHO.

Leave a Reply Cancel reply

Save my name, email, and website in this browser for the next time I comment.

Advertisement

Spread the word, hot discussions.

Recently Updated

Latest from Softonic

About ghacks.

Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.

• Legal Information
• Terms of use
• Privacy Policy
• Cookie Policy
• Cookie settings
• Advertise with Us
• Martin Brinkmann
• Mike Turcotte

How-To Geek

How to enable google chrome flags to test beta features.

Your changes have been saved

Email is sent

Email has already been sent

Please verify your email address.

You’ve reached your account maximum for followed topics.

Why You Need a Longer Password

The internet is not forever, so it's time to preserve what you can, why you shouldn't sign in with google or facebook, key takeaways.

To test out Google Chrome's beta features, enter "chrome://flags" into the address bar, search for the flag you want, and set it to "Enabled." You’ll need to relaunch Google Chrome for the changes to take effect.

The Google Chrome browser has tons of great features, but many of them are not available by default. Chrome "flags" can enable experimental and beta features if you know where to find them. It's surprisingly easy to do.

Google will often put features behind flags before they are ready for prime time. Sometimes these features make their way to stable releases , but they can also disappear without warning. That's the nature of using experimental and beta features.

Related: The Best Chrome Flags to Enable for Better Browsing

There are flags available for different platforms as well. For example, there are certain flags for Chrome on Android, Chrome on Windows, etc. The process for enabling these flags is very simple.

These features are not available to everyone for a reason. They may not work correctly and they can negatively impact your browser's performance. Enable flags at your own risk.

First, open the Chrome browser on your computer, smartphone, or tablet. Flags are available for Chrome on almost every platform, including Windows, Mac, Linux, iPhone, iPad, and Android.

 in the address bar and hit enter.

You will now be on a page titled "Experimental." It's divided into two columns: Available and Unavailable. You can scroll through the "Available" list or search for a specific flag.

When you find a flag to turn on, select the drop-down menu (It will usually say "Default.") and choose "Enabled."

After enabling a flag, you'll need to restart the browser to apply the change. You can enable multiple flags before relaunching. Select the blue "Relaunch" button when you're ready.

That's all there is to it. You've entered a larger world of browser customization. Now go out there and test out potentially upcoming Chrome features!

Related: 10 Useful Flags to Enable in Chrome for Android

• Web Browsers
• Google Chrome

chrome://flags: Try Experimental Features & Activate Debug Tools

What are chrome flags.

Chrome flags can be used to activate additional debugging tools or try out new or experimental features in Google Chrome. That is, you can use them to activate browser features that are not available by default in your Chrome browser.

To use Chrome flags, you need to enter chrome://flags  in the address bar in Chrome and press Enter  to open the Experiments page.

On the chrome://flags page, you can see numerous experimental features. They are set as Default, Enabled, or Disabled. If you are opening this page for the first time, these are the default settings.

Is it normal if Windows 11 23H2 is not showing up in Windows Update on your PC? Let’s see the details together in this post.

How to Enable or Disable Chrome Flags?

To enable or disable an experimental feature, you can use the top search box to search for that feature and then enable or disable it according to your requirements.

You can use these steps to enable or disable Chrome flags:

Step 1: Open Chrome.

Step 2: Go to chrome://flags . You can directly copy and paste  chrome://flags to the address bar in Chrome and press Enter to go to this page.

Step 3: Use the search box to search for the flag you want to enable or disable.

Step 4: Expand the options next to the target flag and select Enabled or Disabled according to your needs.

Step 5: Click the Relaunch button to relaunch your Chrome.

What is chrome//flags settings? How to manage chrome//flags settings to improve your browsing experience? See this guide to get the answers!

Risks of Using chrome://flags

Here is the truth: most Chrome users will never need to use Chrome flags to enable or disable experimental features .

However, if you need to make some changes via Chrome flags, you need to be careful enough. By activating or deactivating features using Chrome flags, you could lose data or compromise your security or privacy. On the other hand, the features you toggle with a flag may stop working or be removed without notice. Due to this, if you are an enterprise IT administrator, you’d better not use Chrome in production.

Tip: Recover your lost data

If your important files get lost after you enable or disable features in Chrome flags or due to some other reasons, you can use MiniTool Power Data Recovery to get them back.

This is professional data recovery software . You can use it to recover files from different data storage devices in different situations. This software has a free edition, which allows you to recover files up to 1 GB without paying any cent.

You can press the following button to get this free file recovery tool and then use it to recover your files.

MiniTool Power Data Recovery Free Click to Download 100% Clean & Safe

When to Use chrome://flags?

If you are a web developer and want to experience the new experimental features before others, or you are just a curious geek, it is worth using Chrome flags to enable these features.

Some Chrome flags can affect the way Chrome looks or works, while some flags can activate new functionality like CSS features or JavaScript APIs. The specified available flags depend on the Chrome version you are using.

If Windows 23H2 fails to install in Windows Update on your computer, you can try the methods in this post to help you solve the problem.

Other Methods to Try Experimental Features in Chrome

Using chrome://flags is not the only method to try experimental features in Chrome. In this part, we will also introduce two more ways to help you enable and try experimental features.

Way 1: Use chrome://flags#enable-experimental-web-platform-features flag

If you want to enable a range of experimental features that don’t have their own flags, you can go to chrome://flags#enable-experimental-web-platform-features  flag in Chrome and then toggle this flag.

Way 2: Use Chrome Beta

Google also tests the featured experiments in Chrome Beta. You can toggle Experiment settings and relaunch Chrome to get these features available.

You can go to this page https://www.google.com/chrome/beta/ and click the Download Chrome Beta  button to download Chrome Beta.

This post introduces the functions of Windows + Ctrl + Shift + B and the time to use it to help you solve issues.

Bottom Line

This is the related information about Chrome flags. If you want to know more information about them, you can let us know in the comments.

About The Author

Position: Columnist

How to Enable Experimental Web Platform Features in Chrome and Firefox

Want to experiment with the latest bleeding-edge web technologies? One way is to download a nightly (or developer) version of the browser. Both Chrome and Firefox have versions of their browsers where they launch experimental or non-standardised features – Chrome Canary and Firefox Nightly respectively. This allows for experimentation and getting feedback before rolling out full support. From time to time, you may need to enable experimental features yourself. This article will show you how to do that in Chrome and Firefox.

What are experimental features?

Browsers sometimes hide new features behind flags – meaning they’re not turned on by default for the majority of users. One example is the CSS Grid Layout Level 1 specification, which (when it was first implemented) was behind a flag in Firefox and Chrome. If we look for this in caniuse.com , we can see that this feature literally has a little flag in earlier versions of these browsers, to denote that it was experimental feature.

While behind a flag, the browser’s implementation of a particular feature may be buggy, and subject to change, but you can still try it out. In fact, if it’s a feature you’re keen to use, the earlier you try it out the better – and if you can give feedback then it’s even more valuable.

Right now, one experimental feature you can try out is subgrid – part of the CSS Grid Level 2 specification. It’s only available in Firefox Nightly, and you’ll need to enable it.

How to turn on experimental features

In your browser, go to the URL about:config . This is the “hidden” settings area for your browser, and enables us to do much more than just enable the CSS features we want to work with - there are many other settings too. But be careful, you could break your browser’s functionality if you don’t know what you’re doing!

If you haven’t visited this URL before, you’ll get a warning that looks like this:

Use the search bar to search for the name of the feature you want to enable. For example, if we search for subgrid we’ll find the following:

The ‘Value’ column on the right determines whether the feature is switched on. Double-click the item to switch the value from ‘false’ to ‘true’. The feature is now enabled.

• Go to the URL chrome://flags . Chrome’s UI is a little more user friendly than Firefox’s here, and it’s quite interesting to read about all the different features that you can enable or disable.

• Switch to the desired setting.

• Best Video Converters
• The Best Video Downloaders for Windows

“Downloading Do Not Turn OFF The Target!” Error In Samsung

• The Best Network Monitoring Tools
• The Best TVs for Xbox Series X

‘IP address conflict’ – How To Manage & Fix

• Best Laptops Under $300
• Best Laptops Under $500

10 Alternatives to Trapcall

• Social Media
• Cut the Cord

TechJunkie is a BOX20 Media Company

Home Web How To Enable And Use Chrome Experimental Features

How To Enable And Use Chrome Experimental Features

We’re all familiar with Google Chrome. It’s one of the most popular browsers on the ‘net and easily one of the best (aside from a few small complaints). Depending on how long you’ve used Chrome, you probably know it like the back of your hand. However, there’s one thing that you might not be familiar with, as it’s not necessarily “easy” to access — Chrome’s built-in experimental features.

Google has actually integrated a ton of experimental features into Chrome which bring, well, some experimental features to the forefront you can use. They can make Chrome more efficient, add new features, and so on. Follow along below, and we’ll show you how to get things setup.

Should you use experimental Chrome features?

So, the question is, should you actually use the experimental features found in Google Chrome? There really isn’t any harm in it — your PC will always be fine, but you may lose your data. Again, they are “experimental” features, meaning they could be buggy or slow down your browser, and possibly delete everything you have — accounts, bookmarks, history, important plugins, folders, etc). That’s not always the case — a lot of the times a buggy experimental feature can easily be fixed. If things start to appear like they’re dragging, it’s (most of the time) as easy as going back into the experimental features section and turning the feature off that is causing the problem. So, as long as you’re willing to tinker around with the features and can risk losing the data in your browser, there’s not too much harm in turning experimental features on.

What about browser backups?

If you want to take experimental features for a spin, but don’t want to take the risk of losing any data, that can easily be resolved by backing up your data with Google’s servers. It’s as easy as logging into Chrome with your Google account (usually found under Settings) and enabling “Sync Everything.” This will sync all of your Google Chrome data (and Chrome OS) with Google’s servers. That way, it’s easily retrievable, allowing you to easily restore your browser to your original settings.

You can find “Sync Everything” under Settings > Sync Settings, as pictured above. Make sure that you have the “Sync Everything” slider turned on. It’ll look blue if it’s enabled, or gray if it’s disabled.

To restore to your original settings, it’s as easy as logging into Chrome again. So, if you turn on an experimental feature, it breaks Chrome, and you have to reinstall, it’s as easy as going back into Settings and logging into your Google account. This will restore your Chrome backup.

Some other general information

One thing to remember before you start using experimental features is that they can be taken away in the blink of an eye — these are features that Google is testing for consumer use in Chrome and Chrome OS. If Google decides that one feature just isn’t working the way they wanted to, you could see it disappear from the list of experimental features available to you. Likewise, you’ll also periodically see new experimental features become available in that list to try.

It’s also worth noting that  a lot  of these experimental features are back-end features, meaning they work to make the overall user experience faster and more efficient. So, you won’t always see features that you can physically use, but that you can turn on for a more overall seamless Chrome experience.

With all of that out of the way, let’s get started!

How to enable experimental features in Chrome

Google’s experimental features are easy to access. Whether you’re running Chrome OS or Google Chrome, it’s as easy as opening the browser and entering  chrome://flags  into the address bar and pressing “Enter.” You should arrive at a page similar to the one shown above.

There’s no specific button you have to press — it’s as simple as going through the list of experimental features, reading what they do, and pressing the “Enable” or “Disable” button, depending on what you want to do with that specific feature.

What experimental features to use

There are a ton of experimental features that you can take for a spin, although some of the descriptions might sound a little confusing as to what they do. We’ve broken down a small sampling of the features below to show you what they do, giving you a better idea of what you’re tinkering around with.

#ignore-gpu-blacklist

This is a software rendering feature that aims to enable GPU acceleration on unsupported configurations. So, it’ll override Chrome’s built-in software rendering list, and instead use your hardware to provide a more overall seamless experience. Obviously this is a back-end feature, trying to increase the overall performance of Chrome; however, right now it appears that it’s a hit or miss with the hardware acceleration being unavailable in many cases.

#enable-scroll-prediction

This is another neat rendering feature to make your Chrome experience a little more seamless. Basically, it predicts where your finger is going to be next so that it can render that portion of the page before you actually arrive there — that way, when you’re ready to view that portion of content, there should be little to know waiting for something to load or “render.”

#smooth-scrolling

Smooth scrolling, so far, is probably the coolest feature. This helps the user smoothly scroll from the top to the bottom of a web page in Chrome, even when your system might be bogging down or struggling to free up resources (i.e. in the case of a full hard drive or lack of memory).

#ash-enable-night-light

We’ve told you before about programs that’ll help you work in the dark, making the screen emit a “warmer” light at night to make things easier on the eyes. One of the features Google is working on for Chrome (for all support operating systems) is something called Night Light, which operates similarly to programs like f.lux. With it enabled, you’ll be able to control the temperature of the screen within Chrome.

#quick-unlock-fingerprint

If you have a Chromebook, this is a neat feature. It’ll allow you to unlock your Chromebook with a fingerprint on the lock screen. Alternatively, there’s another experimental feature that uses a PIN to unlock it.

#print-pdf-as-image

This is another super handy experimental feature that’ll hopefully make it into a full update. It does just as it says, allowing you to print a PDF as an image in Print Preview. This is handy, as sometimes it’s just easier to print a PDF as an image, and some printers out there won’t let you print PDFs, but they will let you print images. This makes that conversion process a little easier. This experimental feature is available in the Chrome browser for all operating systems as well as Chrome OS.

#enable-tablet-splitview

Finally, the last feature we’ll highlight is Split View. This is Chrome OS-specific, allowing you to play or tinker around with using two apps at once in a split view. Again, it’s experimental — a little buggy in our testing — but could be a cool feature for a final update to increase multitasking capabilities.

There’s plenty more experimental features available in Chrome. As a reminder, type in  Chrome://flags  in the address bar to check them out for yourself.

What about the beta channel?

Maybe you don’t want to mess around with experimental features, risking all of your browser data. Or maybe you don’t want to deal with a possible corrupted Chrome client, having to uninstall and reinstall again. But, you still want to tinker with all of the new goodies. Luckily, you can still do that without risking the integrity of your main client — instead, you can download the beta channel.

Google Chrome Beta is a separate client, allowing you to take all of the latest up and coming Chrome features for a test drive. You’ll be able to provide direct feedback to Google on those features as well. It’s honestly the best way to test Chrome’s new features, instead of putting your daily browser at risk.

You can download it for free from Google over at www.google.com/chrome/browser/beta .

And that’s all there is to it! If you like to tinker with new software, Chrome’s experimental features are a great place to start. There’s little risk of “losing all your data,” if you have it backed up and synced into your Google account. And even if you don’t want to mess with these features in the main Chrome client, you can always go and download the Chrome Beta Channel as a separate client, allowing you to still tinker with the new features and enhancements coming down the pipeline.

And keep in mind, Chrome isn’t the only browser you can tinker with, plenty other mainstream browsers off beta features you can mess with as well — Firefox , Opera , Vivaldi, etc.

If you have any feedback or need help getting an experimental feature going, be sure to leave us a comment in the comments section below!

How To Use GeoFilters with Snapchat

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Feb 21, 2018

643 Articles Published

You May Like

How to Get Rid of Generative AI Results in Google

Ashish Mohta

May 21, 2024

How to Take Screenshots of Microsoft Edge Copilot Chat on Android and iOS

May 9, 2024

How to Use Facebook Marketplace Without Facebook Account

Mar 15, 2024

Google Photos: How To View a Hidden Album

Mar 5, 2024

How to Set Up Passkeys For Your Google Account

Ronil Thakkar

Feb 29, 2024

How to Hide From Someone Without Blocking Them on Messenger

Jun 4, 2024

How to Change Emoji Set in Telegram

May 29, 2024

How to Share Collaborative Collection on Instagram With Multiple People

May 27, 2024

How to Change Your Name in Zoom

May 31, 2021

How To Filter By Color in Google Sheets

Robert Hayes

Jan 15, 2020

Copyright @2024 TechJunkie

How To Add Experimental Features In Chrome Using Command Line Switches

Google Chrome and Microsoft Edge stable versions come with experimental features that are not enabled by default. Using Chrome://flags experimental features can be enabled. In case of Edge, you can use Edge://flags in the address bar.

If you are a power user or a system administrator, and you want to enable some of the experimental features across multiple computers, you will need to use command line switches. Unlike the Chrome://flags section, working with command line switches is a little more difficult. Users need to know specific commands and how to execute them.

How to enable experimental features in Chrome (and Edge) using command line switches

Pressing OK on the Shortcut properties will trigger an administrative warning. Press Yes to continue.

The same technique can be applied to Edge browser shortcuts and even Vivaldi and Opera shortcuts as they are also Chromium based browsers. If you are a sysadmin, you can distribute this shortcut across your network to run Chrome with specific experimental features enabled or disabled.

(Cancel Reply)

Get updates in your inbox.

Setting Chrome Flags for Experimental Web Browser Layout Features

Page layouts are set for a revolution. We’re mostly waiting for the majority of browsers to support new layout technologies.

One of those technologies, CSS Flexbox , allows for easy placement and styling of navigation menus, image galleries, photograph thumbnails, centering objects, and so on. Basically, anything that designers would have thought should have straightforward with web design is now possible. 

[caniuse feature=“flexbox”]

While Flexbox can handle the layout within portions of a page, true page layout design is a bit aways. 

The technology powering page layouts, CSS Grids , is still awaiting for browser support.

[caniuse feature=“css-grid”]

However, the latest browser vendors are experimenting with the implementation of the CSS specification with new browser builds. What that means is that web designer and developers can turn them on for testing out cool new stuff like CSS grids!

Enabling Chrome Flags

In the Chrome browser, type in the web address  chrome://flags/ . This action results in a list of experimental browser features available to you.

NOTE: As the warning states at the top of the flags page, these features may go away at any time in a future release. Or worst, they might make your browser something you really do not want it to do like delete data, crash your browser, etc. It’s called experimental for a reason. If we stick to page capabilities, though, that should likely not be that much of a problem.

To turn on CSS Grids, scroll down to Experimental Web Platform features  and select enable.

So that the features can take hold, the browser prompts you to restart the Chrome browser.

To make sure you have browser displaying CSS grids, check out Rachel Andrew’s Grid By Example lab making sure to check out each of her layout examples.

Learn More about CSS Grid

Rachel’s has done a lot of speaking  and  writing about new layout technologies. She even has a great online master class about layouts .

To hear Rachel Andrew’s thoughts on new layout technologies, listen to her interview on the next Non Breaking Space Show episode! Sign up for the The Non Breaking Space’s newsletter or subscribe via iTunes .

About Christopher Schmitt

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications You must be signed in to change notification settings

ACTION REQUIRED: Turn on "Enable experimental Web Platform features" flag in Dartium #734

ussuri commented Jan 17, 2014

sunglim commented Jan 20, 2014

Sorry, something went wrong.

ussuri commented Jan 21, 2014

No branches or pull requests

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

Web Bluetooth - Auto Connect to paired device

Is there a way to auto connect to a paired device with the web Bluetooth ?

So i can get rid of the annoying pop up device selector from google..

• bluetooth-lowenergy
• bluetooth-gatt
• web-bluetooth

As of this moment, I have implemented navigator.bluetooth.getDevices() behind a flag in Chrome. To use the API, the Experimental Web Platform features flag in chrome://flags needs to be enabled. Please follow Issue 577953: bluetooth: Get permitted devices for updates on getDevices().

For reconnecting to a device, I'm also implementing the watchAdvertisements() API to allow apps to receive an Event when system perceives an advertisement packet from device on which this was called on. Please follow Issue 654897: bluetooth: Implement watchAdvertisements() for updates on this API.

These two are part of a bigger project for implementing persistent permissions for Web Bluetooth to allow sites to reconnect to devices that they already had permission to connect to via the device chooser prompt.

• These two APIs are now implemented behind the chrome://flags/#enable-experimental-web-platform-features flag. Additionally, the new permissions backend allows permissions to persist until the permission is revoked in Site Settings or the Page Info dialog box. This new backend is implemented behind the chrome://flags/#enable-web-bluetooth-new-permissions-backend.Use watchAdvertisements() to scan for the device nearby before connecting to it. Please give these a try and file any bugs at crbug.com . –  Ovidio Ruiz-Henríquez Commented Jun 22, 2020 at 23:17
• 1 One more clarification, these APIs are available in Chrome 85.0.4165.0 or higher. So currently Chrome Canary and Chrome Dev channels. –  Ovidio Ruiz-Henríquez Commented Jun 22, 2020 at 23:53
• 2 Can we autoconnect the already paired device, now...! I hope to get a stable api for auto-connection. –  UGandhi Commented May 9, 2022 at 10:11

Your Answer

Reminder: Answers generated by artificial intelligence tools are not allowed on Stack Overflow. Learn more

Sign up or log in

Post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy .

Not the answer you're looking for? Browse other questions tagged javascript bluetooth-lowenergy bluetooth-gatt web-bluetooth or ask your own question .

• The Overflow Blog
• Mobile Observability: monitoring performance through cracked screens, old...
• At scale, anything that could fail definitely will
• Featured on Meta
• Announcing a change to the data-dump process
• Bringing clarity to status tag usage on meta sites
• What does a new user need in a homepage experience on Stack Overflow?
• Feedback requested: How do you use tag hover descriptions for curating and do...
• Staging Ground Reviewer Motivation

Hot Network Questions

• Smooth curve ellipse in geometry nodes with low resolution
• Marie-Sklodowska-Curie actions: publish a part of the proposal just after the deadline?
• Self-descriptive
• Maximizing the common value of both sides of an equation (part 2)
• Querying layer in QGIS Model Designer
• Avoiding USA "gambling tax"
• Base representations, using only limited digits
• How many ways can you make change?
• What happens to entropy during compression?
• How to reconcile the effect of my time magic spell with my timeline
• What is inside the SPIKE Essential battery?
• What does "if you ever get up this way" mean?
• Would reverse voltage kill the optocoupler over long time period?
• Why is the wiper fluid hose on the Mk7 Golf covered in cloth tape?
• Doesn't counting hole and electron current lead to double-counting of actual current?
• Beta function of a marginal operator
• Risks of exposing professional email accounts?
• Why is the stall speed of an aircraft a specific speed?
• Driveway electric run using existing service poles
• Should I install our toilet on top of the subfloor or on top of the PVT?
• Contradiction between the book of Exodus and the book of Ezekiel
• If a Palestinian converts to Judaism, can they get Israeli citizenship?
• What is Zion's depth in the Matrix?
• Fill the grid with numbers to make all four equations true

• Documentation
• What's New?

Android 15 release notes

This page summarizes the major features in the Android 15 release and provides links to additional information. These feature summaries are organized according to the feature's documentation location on this site.

Architecture

Deprecation of vndk.

Android 15 deprecates VNDK. Former VNDK libraries are treated same as other vendor or product libraries. See Vendor NDK for more details.

Enable 16KB page size

Android 15 and higher have support for building Android with a 16KB page size.

For more information, see Enable 16KB page size .

Vendor overlay

Android 15 deprecates vendor overlay.

Head tracking over LE audio

Android 15 provides support for latency mode adjustments for head tracking (HT) based on whether the LE-ACL or LE-ISO transport mechanism is used. See Head tracking over LE audio .

Android Automotive power policy

Updated the Android Automotive Power policy for Android 15 with two new system power policies: no user interaction and suspend prep .

Content for HD and DAB radio

Android 15 includes improvements to HD radio support in the broadcast radio HAL and a sample unbundled radio app, which can be used as a reference for radio control implementation.

For more information, see Automotive Radio .

Android camera feature combination query API

Starting in Android 15, the Android platform provides an API to query camera feature combinations. This API lets camera clients query whether a specified combination of camera features can be supported by the device.

For more information, see API to query feature combinations .

Low Light Boost

Android 15 introduces Low Light Boost, a new auto exposure mode that can be implemented in Camera2 in the HAL, and as part of a camera extension such as night mode. Low Light Boost automatically adjusts the brightness of the Preview stream in low-light conditions.

For more information, see Low Light Boost .

Compatibility

Camera its updates.

Android 15 introduces updates to Camera ITS tests , which include new and updated tests.

For more details, see Android 15 Camera Image Test Suite Release Notes .

Immersive audio test case

Starting in Android 15, a new CTS Verifier test for verifying spatial audio head tracking latency is introduced.

For more information, see the CTS Verifier for head tracking latency test .

New CTS Verifier audio tests

The following audio tests and supporting pages are added to the CTS Verifier documentation:

• CTS Verifier audio data paths tests
• CTS Verifier multichannel mixdown test
• Audio loopback latency test

Connectivity

Android packet filter v6.

Android 15 introduces Android Packet Filter (APF) v6, which includes counters for debugging and metrics and support for packet transmission. For more information, see Android Packet Filter .

Android proprietary NCI commands

Android 15 adds new Android proprietary NFC Controller Interface (NCI) commands to interact with an NFC controller. For details on the specifications of these commands, see Android proprietary NCI commands .

Domain selection service

Android 15 adds the DomainSelectionService system API, which lets you implement domain selection between the IMS service and legacy services over circuit switched networks.

For more information, see Domain Selection Service .

Subscription-level carrier service capabilities

Starting in Android 15, carriers can specify the service capabilities of the device at the subscription level. This lets app developers customize the user experience of apps based on the available capabilities for the subscription, in addition to at the device level.

For more information, see Subscription-level service capabilities .

Support for 802.11az in Wi-Fi RTT

Starting in Android 15, Wi-Fi Round Trip Time (RTT) supports the IEEE 802.11az protocol. For further information, see Wi-Fi RTT .

Watch companion device profile update

Android 15 adds the POST_NOTIFICATIONS permission to the watch profile . For details, see Companion Device Profiles .

Snapshot and restore on Cuttlefish devices

Android 15 adds support for taking and restoring snapshots of Cuttlefish virtual devices. Taking a snapshot of a Cuttlefish device lets you save the state of the device in an image on disk. You can then restore the snapshot to bring up a Cuttlefish device to the previously saved state.

For more information, see Cuttlefish: Snapshot and restore .

NFC support for Cuttlefish devices

Android 15 introduces support for NFC on Cuttlefish devices. The Cuttlefish NFC feature uses Casimir, an external NFC device simulation tool.

For more information, see Cuttlefish: NFC .

WebSQL WebSettings deprecation

Starting in Android 15, the WebSettings methods setDatabaseEnabled and getDatabaseEnabled , which are used for WebSQL support inside WebView, are deprecated. WebSQL is removed in Chrome and deprecated on Android WebView. These methods will become no-ops on all Android versions after support is removed in Chromium.

The World Wide Web Consortium (W3C) encourages apps needing web databases to adopt other storage alternatives like IndexedDB .

Support for variable fonts

Starting in Android 15, variable fonts are rendered at runtime with better efficiency and granularity. The font configuration file fonts.xml is being deprecated. See Implement custom fonts for more information.

Interaction

Head tracker hid protocol 2.0.

Android 15 introduces version 2.0 of the head tracker HID protocol, which includes support for Bluetooth LE audio. For more information, see Head Tracker HID Protocol .

Neural Networks API deprecation

Starting in Android 15, the Neural Networks API (NNAPI NDK API) is deprecated. The Neural Networks HAL interface continues to be supported and NNAPI drivers aren't affected by this deprecation.

For more information, see the NNAPI Migration Guide .

OEM guidance for RoI implementation

Android 15 introduces a standardized process for integrating region of interest (RoI) user configurations into the Android video encoding framework. For further information, see OEM guidance for RoI implementation .

Permissions

Platform-signed shared uid allowlist.

Android 15 introduces an explicit allowlist for platform-signed nonsystem apps to join (platform-signed) shared UIDs.

For more information, see Platform-signed shared UID allowlist .

Requirements update for COMPANION_DEVICE_APP_STREAMING and COMPANION_DEVICE_NEARBY_DEVICE_STREAMING roles

Android 15 updates the Virtual Device Manager role policies to prevent misuse for fraudulent purposes.

For more information, see COMPANION_DEVICE_APP_STREAMING and COMPANION_DEVICE_NEARBY_DEVICE_STREAMING on Android Roles .

Signature permission allowlist

Android 15 introduces an explicit allowlist for platform signature permissions that are requested by nonsystem apps or newly requested by updates to system apps.

For more information, see Signature permission allowlist .

setAdjustCompilerFilterCallback

Starting with Android 15, you can override the compiler filter for certain packages using the setAdjustCompilerFilterCallback API.

For more information, see Override the compiler filter for certain packages .

Carriers can no longer hide the 2G toggle from users. The carrier configuration key KEY_HIDE_ENABLE_2G has been deprecated.

dusize_4k flag

Android 15 introduces the dusize_4k flag which forces the encryption data unit size to be 4096 bytes even when the file system block size is not 4096 bytes.

For more information, see Internal storage .

Mobile Network Ciphering and IMSI Disclosure Transparency

Mobile network protocols up to and including 5G allow user data (including calls, SMS, data connections, and certain signaling-based metadata) to be transmitted in cleartext with encryption and integrity protection disabled.

Android 15 introduces new network and privacy settings that enable notifications for users when they connect to an insecure mobile network (no encryption or integrity protection where there is otherwise an expectation that this would be used), and their private identifiers (IMSI, IMEI, or SUCI) are exposed to the network in a manner that could potentially be used to track users.

The international mobile subscriber identity (IMSI) is a unique number used to identify every user on a certain cellular network tied to a user's SIM card. Attackers can capture this number in transit, and this is the basis for many known cellular attacks. The international mobile equipment identity (IMEI) is the unique identifier tied to a mobile device. The Subscription Concealed Identifier (SUCI) is a 5G-specific identifier.

Private space

Private space is a secure area for sensitive apps, where users can hide apps from unauthorized access. You can use private space to store sensitive apps such as banking, dating, and other personal apps that you don't want other device users to access.

For more information, see Private space .

Virtual A/B version 3

Android 15 introduces a a new version of Android virtual A/B update mechanism. This new feature introduces faster, smaller and more performant OTA updates. For more information, see Virtual A/B .

Virtualization

Enhancements to android virtualization framework (avf).

Android 15 introduces the following enhancements to Android Virtualization Framework (AVF), the framework for managing virtual machines (VMs).

Updatable VM: VMs can keep their secrets and data protected by them even across updates in their software stack. For more information, see Updatable VM .

VM remote attestation: Clients of a VM can be sure that they are communicating with the correct VM and software stack running on a trusted device. Clients can use the attestation to make sure that, for example, they only deliver a valuable machine learning model directly to their trusted VM. For more information, see VM remote attestation .

Device assignment: Peripheral devices can be fully assigned to a protected VM. Such an assigned device isn't accessible from outside of the VM, and the device itself can access only the memory that is owned by the VM. This feature can be used to run machine learning accelerators like a GPU in a protected VM, without having to send the code and data out of the VM. This feature is experimental and its availability highly depends on the capability of the hardware and the support from the chipset and device makers. For more information, see Getting started with device assignment .

Content and code samples on this page are subject to the licenses described in the Content License . Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.

Last updated 2024-08-29 UTC.

• Español – América Latina
• Português – Brasil
• Tiếng Việt
• Chrome for Developers

Introducing hints, Related Origin Requests and JSON serialization for WebAuthn in Chrome

Chrome 128 and 129 introduces exciting new features for WebAuthn—the underlying API to build passkey-based authentication systems.

• Hints : Hints give relying parties (RPs) better control over WebAuthn UI in the browser. They are especially helpful for enterprise users who want to use security keys.
• Related origin requests : With related origin requests, RPs can make passkeys valid on multiple domains. If you own multiple sites, you can now enable your users to reuse their passkey across your sites, eliminating login friction.
• JSON serialization : JSON serialization APIs let you simplify an RP's frontend code by encoding and decoding options and credentials passed to and from WebAuthn API.

With hints , relying parties (RP) can now specify UI preferences for creating a passkey or authenticating with a passkey.

Previously, when an RP wanted to restrict the authenticator the user can use to create a passkey or to authenticate with, they could use authenticatorSelection.authenticatorAttachment to specify "platform" or "cross-platform" . They respectively limit the authenticator to a platform authenticator or a roaming authenticator . With hints , this specification can be more flexible.

The RP can use optional hints in the PublicKeyCredentialCreationOptions or PublicKeyCredentialRequestOptions to specify "security-key" , "client-device" and "hybrid" in a preference order in an array.

The following is an example credential creation request that prefers "cross-platform" authenticators with "security-key" as a hint. This tells Chrome to show a security key focused UI for enterprise users.

When an RP wants to prioritize a cross-device verification scenario, they can send an authentication request that prefers "cross-platform" authenticators with "hybrid" as a hint.

Related origin requests

With Related Origin Requests , RPs can make passkeys usable from multiple domains. Building a centralized login experience and using federation protocols remains the recommended solution for most sites. But if you own multiple domains and federation isn't possible, related origins may be a solution.

All WebAuthn requests must specify a relying party ID (RP ID), and all passkeys are associated with a single RP ID. Traditionally, an origin could only specify an RP ID based on its domain, so in that case www.example.co.uk could specify an RP ID of example.co.uk , but not example.com . With Related Origin Requests, a claimed RP ID can be validated by fetching a well-known JSON file located at /.well-known/webauthn from the target domain. So example.co.uk (and example.in , example.de , and so on) could all use an RP ID of example.com if example.com specifies them in the following format:

URL: https://example.com/.well-known/webauthn

Learn how to set up Related Origin Requests at Allow passkey reuse across your sites with Related Origin Requests .

JSON serialization

WebAuthn request and response objects have multiple fields that contain raw binary data in an ArrayBuffer, such as the credential ID, user ID, or challenge. If a website wants to use JSON to exchange this data with its server, the binary data must first be encoded, for example with Base64URL. This adds unnecessary complexity for developers that want to start using passkeys on their websites.

WebAuthn now offers APIs to parse PublicKeyCredentialCreationOptions and PublicKeyCredentialRequestOptions WebAuthn request objects directly from JSON, and serialize the PublicKeyCredential response directly into JSON. All ArrayBuffer-valued fields that carry raw binary data are automatically converted from or to their Base64URL-encoded values. These APIs are available from Chrome 129.

Before creating a passkey, fetch a JSON encoded PublicKeyCredentialCreationOptions object from the server and decode it using PublicKeyCredential.parseCreationOptionsFromJSON() .

Browser Support

After creating a passkey, encode the resulting credential using toJSON() so that it can be sent to the server.

Before authenticating with a passkey, fetch a JSON encoded PublicKeyRequestCreationOptions from the server and decode it using PublicKeyCredential.parseRequestOptionsFromJSON() .

After authenticating with a passkey, encode the resulting credential using toJSON() method so that it can be sent to the server.

To learn more about WebAuthn and passkeys, check out the following resources:

• Passkeys | Chrome for Developers
• Introduction to server-side passkey implementation
• passkeys.dev

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2024-08-30 UTC.