4 ms·

Could you point me to an example of Chrome "UI rearranging itself at random"? The only time I've had issues with chrome, is when I switched to the dev stream..

by Volpe 14y ago

Could you point me to an example of Chrome "UI rearranging itself at random"? The only time I've had issues with chrome, is when I switched to the dev stream... Stable has always been, well, stable.

Silhouette 14y ago
I was speaking figuratively, referring to the way Chrome alters its UI during updates. Those updates happen in the background, so you can literally close your browser one day, and then open it the next to find something has changed. In Chrome's case, the most obvious changes lately always seem to be adding junk like apps or a web store or logging in (logging in... to my browser... yes, really). I have no need of or interest in any of these things, yet they now clutter up the UI where once they did not.
- LeonidasXIV 14y ago
  > I was speaking figuratively, referring to the way Chrome alters its UI during updates. Those updates happen in the background, so you can literally close your browser one day, and then open it the next to find something has changed. If you can't back up your argument with something substantial, then don't mention it. Automatic updates are an actual feature of Chrome and for a good reason. I wouldn't call updates "rearranging the UI at random". And the rest is also complete useless, because your "bug" essentially is that Chrome changes. Well duh! You might not like logging in to a browser, and I can see the point. But that is not a bug in Chrome.
  - Silhouette 14y ago
    But that is not a bug in Chrome. No, and I didn't say it was. The bugs I was talking about are things like stopping playing a short HTML5 video before reaching the end, or failing to send basic event notifications to JavaScript before handing control off to the Java plug-in because the user interacted with an applet. Both of these are regressions in things that used to work, and they fundamentally break the behaviour of web apps using those features. And of course, there have also been numerous rendering problems with everyday CSS in Chrome: banding in linear-gradients, inability to use fractional letter-spacing, I've lost count of how many attempts to get border-radius working properly, etc. These are what I would class as cosmetic issues rather than "serious" ones that actually break functionality like the ones I mentioned before, but they're still things where Chrome is coming in a fairly poor third place in quality of implementation today. None of these is exactly a big secret or somehow overlooked in the Chrome and/or upstream bug trackers, as a quick Google search for any of the symptoms I've just mentioned will rapidly confirm. In fact, the letter-spacing one was first reported in WebKit Bugzilla more than four years ago and remains unfixed today.

by Volpe 14y ago

Could you point me to an example of Chrome "UI rearranging itself at random"? The only time I've had issues with chrome, is when I switched to the dev stream... Stable has always been, well, stable.

Silhouette 14y ago

I was speaking figuratively, referring to the way Chrome alters its UI during updates. Those updates happen in the background, so you can literally close your browser one day, and then open it the next to find something has changed. In Chrome's case, the most obvious changes lately always seem to be adding junk like apps or a web store or logging in (logging in... to my browser... yes, really). I have no need of or interest in any of these things, yet they now clutter up the UI where once they did not.

LeonidasXIV 14y ago
> I was speaking figuratively, referring to the way Chrome alters its UI during updates. Those updates happen in the background, so you can literally close your browser one day, and then open it the next to find something has changed. If you can't back up your argument with something substantial, then don't mention it. Automatic updates are an actual feature of Chrome and for a good reason. I wouldn't call updates "rearranging the UI at random". And the rest is also complete useless, because your "bug" essentially is that Chrome changes. Well duh! You might not like logging in to a browser, and I can see the point. But that is not a bug in Chrome.
- Silhouette 14y ago
  But that is not a bug in Chrome. No, and I didn't say it was. The bugs I was talking about are things like stopping playing a short HTML5 video before reaching the end, or failing to send basic event notifications to JavaScript before handing control off to the Java plug-in because the user interacted with an applet. Both of these are regressions in things that used to work, and they fundamentally break the behaviour of web apps using those features. And of course, there have also been numerous rendering problems with everyday CSS in Chrome: banding in linear-gradients, inability to use fractional letter-spacing, I've lost count of how many attempts to get border-radius working properly, etc. These are what I would class as cosmetic issues rather than "serious" ones that actually break functionality like the ones I mentioned before, but they're still things where Chrome is coming in a fairly poor third place in quality of implementation today. None of these is exactly a big secret or somehow overlooked in the Chrome and/or upstream bug trackers, as a quick Google search for any of the symptoms I've just mentioned will rapidly confirm. In fact, the letter-spacing one was first reported in WebKit Bugzilla more than four years ago and remains unfixed today.