Mark as "unsupported" flags Vivaldi can't use
-
Or even better, totally hide them.
I mean everything won't work with vivaldi like:
- Chromium bookmarks&history (we have our)
- Chromium tabs flags (which won't work)
- Chromium UI flags (not applicable on Vivaldi)
- Chrome Sync (which Vivaldi hasn't)
- G-Services (if not used by Vivaldi)
- NACL flags (works only on chrome)
- Omnibar/omnibox flags (as Vivaldi don't use chromium UI)
Having such flags in the wild may confuse users as they wonder why a flag for [chromium] UI don't work on Vivaldi. And crowd the list.
-
@Hadden89 The base chrome browser is still available in Vivaldi, so technically these flags are all actually supported. It's just that they're not relevant to Vivaldi users.
It's also worth noting that flags aren't really supposed to be used by anyone except developers , so I'm not sure it is worth the effort to go through them every time chrome updates to change which are relevant and which are not. They are chosen largely at the whims of the Google developers. The only ones that are truly relevant to vivaldi are the entires in
vivaldi://experiments
. -
@LonM said in Mark as "unsupported" flags Vivaldi can't use:
The base chrome browser
You surely meant Chromium, we all know Chrome is more than just the Chromium engine.
-
@Gwen-Dragon err... ok, I guess. I don't know what harm there is on pointing that out.
-
@LonM That's also true. Maybe a blog post which explain why most things there are not supposed to work?
-
@Gwen-Dragon said in Mark as "unsupported" flags Vivaldi can't use:
@Hadden89 said in Mark as "unsupported" flags Vivaldi can't use:
Maybe a blog post which explain why most things there are not supposed to work
If a user has enough knowledge to investigate. I guess the team has less resources yet. But you may write to Vivaldi Support to ask for a article.
Related to this,
It would be helpful a Topic to share about them by those users whom tested.Even, a Topic per Flag - to keep it clean -.
-
@iAN-CooG Actually I don't. I have never (personally) used chrome. When I was working I did have to go users sites to find out they'd installed chrome and our IE/Firefox supported services wouldn't work and uninstall it.
-
Technically, as i understand it, none of the flags are supported. They're experimental features and flags are coming & going all the time. As such, I wouldn't think it worth Vivaldi's time to do much of anything to that page. People can modify those flags if they like, but if it causes issues, I would expect any development response to be to set the flag back to default. Unless the feature in question had a firm commitment by the Chromium team to incorporate it into the main part of the browser in an upcoming release, then they might take the opportunity to start investigating any issues to resolve them by the time Vivaldi upgrades to whatever future Chromium release pulls it into the supported browser functionality. Though setting it back to default would still be the answer until said release.
The top of the page displays an important warning to anyone who is thinking about manipulating these flags.
WARNING: EXPERIMENTAL FEATURES AHEAD!
By enabling these features, you could lose browser data or compromise your security or privacy.