New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 341 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Dec 2013
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment

Provide a way to disable Instant Extended API (new tab page)

Reported by jerzyglo...@gmail.com, Dec 7 2013

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1729.3 Safari/537.36

Steps to reproduce the problem:
1. Open new tab page.
2. See the big Google logo and search bar and small thumbnails below.
3. Want to revert the old new tab page with bigger thumbnails.

What is the expected behavior?

What went wrong?
Please allow us to revert to the good old new tab page with bigger thumbnails and recently closed tabs menu, instead of the new one with redundant search bar, by providing the "disable-instant-extended-api" or similar flag.

Did this work before? Yes Chrome 31

Chrome version: 33.0.1729.3  Channel: dev
OS Version: 6.2 (Windows 8)
Flash Version: Shockwave Flash 11.9 r900

 
Labels: Cr-UI-Browser-Instant-Extended
-> User Feedback.

Comment 2 by sush...@gmail.com, Dec 8 2013

I am not a fan of the Chrome App Launcher. I mean I do not hate it but I prefer seeing apps on the new tab page instead of the search box which is totally redundant because I can search from the omnibar. 

Comment 3 by Deleted ...@, Dec 8 2013

I really hate chrome's new tab page, no logic at all and it's very ugly too.

Comment 4 by Deleted ...@, Dec 8 2013

I completely agree with this issue.
stopthat.jpg
125 KB View Download
Labels: -Type-Bug Type-Feature

Comment 6 by Deleted ...@, Dec 9 2013

the new crappy start screen is a huge leap backwards! Well done!!!

Comment 7 by nee...@gmail.com, Dec 9 2013

Proof it's not a bug, but intentional:  http://src.chromium.org/viewvc/chrome?revision=236116&view=revision

This is really ridiculous. There isn't a way to see previously closed tabs or synchronized tabs from other devices without extra clicks and drilling. This should definitely be an option with a simple check-box. Also can't see installed Chrome Apps.

Comment 8 Deleted

Comment 9 Deleted

Owner: odean@chromium.org
Status: WontFix
Thanks for the feedback.  There are no plans at the moment to provide a way built into Chrome to change the new tab page.  You can find a number of alternative New Tabs in the web store: https://chrome.google.com/webstore/search-extensions/new%20tab

Many of the issues here have been previously discussed on https://code.google.com/p/chromium/issues/detail?id=298409.
It's a pity you are forcing us to use the new NTP.

Fortunately, there is a workaround: install New Tab Redirect (https://chrome.google.com/webstore/detail/new-tab-redirect/icpgjfneehieebagbmdbhnlpiopdcmna) and set the URL to: chrome-internal://newtab/
Tada! Now we have the good old NTP!
Thanks jerzyglowacki.  That workaround worked for me.  I'll never understand why Google would force users to 3rd party extensions to regain functionality they formerly had directly in Chrome.  Let's hope they don't get rid of the chrome-internal://newtab.

Comment 13 by zju...@gmail.com, Dec 17 2013

bring back the old newtab. there are too many drawbacks of the new design, list some here.
 1, It's really inconvenient to reopen my last closed tabs compared to before. 
2, the thumbnail of the new design is too small, not decent as  predecessor . 
3, the search box of the new tab is such a redundance of the omnibox. 
4, the reaction is slower than before.

I dont need the google logo on my new tab although i love google so much. So bring back the old design, or at least provide a option to switch back.
zju...@gmail.com, you have workaround above. Though I personally recommend another extension with same purpose: <https://chrome.google.com/webstore/detail/new-tab-redirect-plus/hnpoebddognhfcnfbfjdbgmgadkmmdkj> because this one doesn't use additional memory.
This is literally the most ridiculous issue I´ve ever seen and Google´s stubbornness is astounding. Fortunately, I´ve just installed the extension from the previous comment and things are back to normal.

A giant ´boo´ to Google for forcing us to do this.

Comment 16 by nee...@gmail.com, Dec 17 2013

This should, at least, be an option in settings. Have the default NTP be whatever the Chromium team wants, but have the option for power users to flip it.
It's even worse now. In 33.0.1750.0 (Developer Build 241148) (or a little earlier) chrome-internal://newtab isn't available anymore.

Hope someone will release it as an extension.

Comment 18 by nee...@gmail.com, Dec 18 2013

Thanks for the heads-up. I figured it was only a matter of time. I still don't get the logic of stripping it completely out, besides "do it this way, and this way only".

Comment 19 by nee...@gmail.com, Dec 18 2013

And here it is, the removal of the chrome-internal scheme :  http://src.chromium.org/viewvc/chrome?revision=240819&view=revision
At the moment, I am quite happy using the 
chrome://flags/#enable-instant-extended-api (disable then restart)
technique. No extension needed, wretched NTP gone, karma restored.

Clearly, we're not going to get an explanation of WHY the the disastrous and universally-detested NTP was forced upon us, but can the devs please confirm that the #enable-instant-extended-api flag will remain in future build to allow it to be switched off?
In the latest dev release, that flag (chrome://flags/#enable-instant-extended-api) is gone.  They've also now removed chrome-internal://newtab, so even the extension suggestion from earlier in this post doesn't work.  

Basically, they've completely killed off the good NTP in favor of the newer, less functional, and redundant one.  I'm going to give Firefox a try again.  This is the strangest product decision I can recall ever seeing a software company make.  
If it IS the case that chrome://flags/#enable-instant-extended-api is gone and remains gone, then I've just switched from "meh, at least there's a way this mess" to "screw this, I'm off".

Like you, I can't fathom this out. The only thing I can think of is that Google and the Chromium Project want to kill the project off and this is a way of reducing the numbers. Seems a daft way to do it, but, apart from killing off Google Reader, I can't think of one single thing so unpopular that remains unexplained and unreverted.

Yes, I know they're always messing with Youtube, and the latest change to comments is so bad I don't bother with comments now. But this NTP change is a whole different league and I'm not exaggerating when I say I haven't one SINGLE user with anything good to say about it.

Seeing as it's open source, can we not trace this change back to a log entry or ticket or user or something?

Comment 23 by tob.l...@gmail.com, Dec 18 2013

Yes, this decision from Google is totally insane! Do they WANT to piss their users off?! And they are even *going out of their way* to do it! Unbelievable! 

I personally will absolutely refuse to use the new NTP as I find it horrible (mostly for lacking quick access to "Other devices" and "Recently closed" down in the right hand corner)!

While I love Chrome, I honestly think I'll have to switch to some other browser if Google decides to make it impossible for us to use the old NTP (or a proper replacement).
Dudes, seriously, wtf!? Supertiny thumbnails and removal of recently closed tabs? I mean c'mon. The first time I saw the new NTP I thought to myself. Oh'well they are just testing some new stuff (and that's okay, I like when you experiment with new stuff), they will probably realize having supertiny thumbs and removing one of the most used feature, wasn't a good idea and revert back to the old NTP. But a couple of weeks(months?) later they're still using this new crappy NTP. If you're doing this for the big masses becuase they don't know how to use the omnibar please stop. There are better ways to educate the more not tech-savy people than to completely destroy a working design.
angry.png
18.9 KB View Download

Comment 25 by Deleted ...@, Dec 24 2013

i hate this
I can hardly wait for the shitstorm awaiting Google when this gets into the beta and then into official channel. Seeing how only people who use dev channel see this now, the number of protests is relatively small, but each further group (beta then official) should be exponentially bigger. Dear Google, enjoy :)
2013 The year Google truly turned evil
Labels: -Via-Wizard Restrict-AddIssueComment-Commit
Cc: ashej...@chromium.org
 Issue 335251  has been merged into this issue.
 Issue 335251  has been merged into this issue.
 Issue 335251  has been merged into this issue.
 Issue 346972  has been merged into this issue.

Sign in to add a comment