3 ms·

> Most of the issues I've had with Chrome can't be changed with flags. Do you have anything to back up that statement? Until you specify what those features ar

• Dylan16807 8y ago
  Let me quote "that statement". > People have been bitching about Chrome too, and those things they were bitching about can also be disabled using flags. That is what I asked for evidence of, the things most people are complaining about being fixable with flags. I didn't ask for evidence of my own issues.
  • chc 8y ago
    It would be much easier for you to give an example of a major problem people have with Chrome that can't be fixed with a flags, rather than ask them to exhaustively list issues that can be fixed with flags. It's not a very reasonable ask IMO. If you think they're wrong, just show your cards.
    • Dylan16807 8y ago
      My own list isn't very long, which is why I want to know what nahalz was basing their argument on. I think it would work better than me searching from scratch. But I know you can't change the UI around and no flags will help those many issues. There was a flag I used once to good results that later got removed, but I don't remember what it was. They've been messing around with autoplay and flash with no way to override. Especially obnoxious is that if you directly visit a .swf it's impossible to make it play. I'll try to remember the rest. On the plus side a bit of testing just now has made me aware that "site per process" and "process per site" do nearly opposite things, and the one that saves memory does actually still function. (The flag is the one I don't want, though, heh.)