googlelobi.blogg.se - Project fugu

#Project fugu software#
#Project fugu trial#

Limited across all users globally to ensure they don't become a de facto standard, so it's recommended you activate the feature in your codebase following each browser's trial guidelines for a subset of your users.Stable enough to use with real users, but they may change throughout the course of the trial.So where possible, you should implement feature detection or graceful degradation to handle the case when the feature is unavailable. Experimental, they may change and may become unavailable, including not extending beyond the experiment, and may be unavailable for some time, even if they are eventually enabled for all users.

Origin trials allow you to try out new features and give feedback to the web standards community on usability, practicality, and effectiveness.

An origin trial: a state where features can be enabled by origin, developers can run tests for a wider audience than their single browser instance, but the feature is still being tested and the implementation can change, more details below.

Because such features are still under development, changing flag defaults can have unanticipated consequences for the stability of the browser. Under no circumstances should users ever be told to turn flags on or off. You can enable or disable flags on Chromium-based browsers by going to about:flags, allowing you to test on your own browser instance.

A developer trial: the feature is behind a flag, the API isn't necessarily stable, and you shouldn't implement it for real users.

The process for each capability #īefore launch, there are two states an in-progress API could be in, and both allow you to test them.

What if you want to request a new capability? You can file an issue in the Chromium bug tracker, or you can go to webwewant.fyi and fill out a form to reach the corresponding browser vendors.

Links and additional information for each API.

The status of each API being worked on or considered.

There is a public tracker to keep up with all the work to ship new capabilities. The capabilities project, or Project Fugu, is a cross-company effort to make it possible for web apps to have the same capabilities as platform-specific apps by exposing the capabilities of these platforms to the web, while maintaining user security, privacy, trust, and other core tenets of the web. This is where the capabilities project, known as Project Fugu, comes in.

#Project fugu software#

This approach also loses the reach of the web, often being forced to choose what devices and operating systems to support, which often require different wrappers, and which further expands the security and maintenance burden.įilling these capabilities gaps is the key to fixing this and thereby enabling the web to be the software platform of the future, covering as many use cases as possible, in comparison with platform-specific SDKs. This will also force them to take on the additional security and maintenance burden of keeping both the browser fork and wrapper up to date. Those who want to develop for the web but need more different capabilities are forced to bundle their web apps in wrappers and publish them in app stores.ĭevelopers may choose to ship their own custom browser as platform-specific apps, which disproportionately increases the size of their web apps.

The web is a powerful platform, but there are still gaps in what it can solve.