Can hardly wait for this to get to Stable and uproar that will be heard about the menu spacing issue and then they can't even disable with the use the command -–disable-new-menu-style
Give Us our New New Tab Page Back!
2Patrickchrome://flags/Enable Instant extended API -> Disable
@ Google and to anyone it concerns:How is it that there have been Chrome STABLE channel updates on Linux but no stable channel update posts around here?You announced Chrome 28 stable for Linux in your "oh, and we changed requirements for Chrome on Linux" post, but you failed to document and communicate the two or three updates that happened after that.Ya know guys, it would actually be incredibly great to know about what got fixed or broken.
@Jochen Blacha U can see the list of bug fix in SVN revision log above. It's kind of a text for developer but it show the fixed bugs.
I'm really confused... last night (27th) my stable channel (27) got updated... now it reads 28.1500.63 m. When I do a chrome://version it does not have any beta or dev monicker. There is no mention of a stable channel release of 28... and the only mention of a 28.1500.63 is this beta channel but mine doesn't indicate it's a beta. Also finding it very slow... sometimes freezes for about 60 seconds when I right-click the address bar.I'm very upset if in fact my browser updated itself to the beta channel. I've always been on the stable channel and don't appreciate being switched over without my consent.
Hi, I have the same problem as "Kdata Traveler". Until a week ago I had the stable version 27. Last Friday Chrome made an update to version 28! But I had never installed a beta version of the browser! Currently I have the version: 28.0.1500.63.What should I do so that I only get back the stable version of Chrome? Sorry for my English!
I want the new tab page back please, with G+ notifications.
I just do not understand why an unstable package has been assigned to Linux version where you have already selected the stable package selection.Beside that, those bugs issues has never been mentioned.
I just want to say to the Chrome devs that the new new tab page; the one similar to the Google homepage, should be here to stay. I've just checked Canary and for whatever reason, possibly random, the default new tab page is the old/current one.I see people protesting in comments, but there are always going to be people who complain at change, even when it's positive. The old/current new tab page has always been one of the only clunky ugly things in Chrome, apps don't need to be so big and central for how much use they get, and it doesn't need to have such a crowded and legacy-looking UI or be so slow to access. Considering half the world's homepage is Google for a reason, it makes sense for Chrome's new tab page to take a note from this book. The new new tab page fits with Chrome's vision of being simple and fast, and the old/current one is neither.
Will, not everyone wants a redundant search field and logo taking up half of their tab page. Glad it's gone.
Post a Comment