13 ms·
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 bugtrac
by nolist_policy 3y ago
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.
- keepamovin 3y agoInteresting! Could you give a few anecdotes and a list of flags that seem to provide a bit of stability? Would be useful and insightful I think :)
- nolist_policy 3y agoIt'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: #top-chrome-touch-ui - disabled #focus-follows-cursor - enabled #crostini-qt-ime-support - enabled #crostini-virtual-keyboard-support - enabled
- keepamovin 3y agoCool! Thanks :)