Chrome flags also apply to chromeos and most development happens behind them.
I'm on the chromeos beta channel and often when I report something on the bugtracker there will be a comment like "Hey, can you try with flag #xyz disabled". It often works which is nice for me because it fixes the bug and nice for them to pinpoint the cause.
It's only short-term, for example the USB permission code got reworked (#permissive-usb-passtrough flag) and I couldn't pass my USB serial adapter to the Linux environment (crostini) anymore. Or there where minor issues when the terminal got reworked (#terminal-alternative-emulator).
So I had to disable that flag until the bug got fixed and the fix deployed.
But there are more flags too that I have changed long-term:
This article is pretty well written, gives lots of good examples, is concise, links to highly useful resources and introduces the complexity around distinctions between flags, settings, features etc.
Ahh yes, Google Chrome flags like picture in picture, notable for being hidden behind a paywall by google on every platform where they can get away with it. How forward thinking…
I'm on the chromeos beta channel and often when I report something on the bugtracker there will be a comment like "Hey, can you try with flag #xyz disabled". It often works which is nice for me because it fixes the bug and nice for them to pinpoint the cause.
reply