cVim does not work on the default new tab page

[breandan]

When the user opens a new tab via Ctrl+T, the plugin does not work.

[cedric-sun]

It seems to have been fixed in the latest release.

And I think it would be better to open a new tab by t of cVim. Chrome always focus on the address bar when a empty new tab is open (such as by clicking the new tab button or C-T), which is one of the most annoying features in Chrome. BTW another one is that there is no shortcut to focus back on the page (from the address bar or debugger), there are several hacking, but not always desirable.

[schmitmd]

I'm experiencing the same. Opening tabs via "t" from cVim does work, but sadly I sometimes still have to use my mouse :disappointed: . The "focus back on page" item is also something that would save me a few seconds' effort (which adds up, obviously).

[nesqi]

Fixed in what release?

Also, are you talking about cVim or chrome?

[Tiberriver256]

Still happening for me on Chrome 63.0.3239.132

[breandan]

One solution is to disable the new tab page via a plugin like Shortkeys, by binding the shortcut Ctrl+T to "Do Nothing".

[huigeek]

that's what happened to me，Chrome 72.0.3626.121

[crabdancing]

Can confirm this issue as of 73.0.3683.75.

Edit: some very interesting things -- this does not happen when I open a blank new tab via t[enter] -- that just loads a blank.html within the extension itself. However, if I open a new tab via the plus icon or by pressing Ctrl+T, many extensions are disabled on that page -- just like they're disabled in the Chrome Web Store.

It's probably a 'feature' in Chrom{e,ium} itself, to "protect" us whether or not we actually need protecting (as usual). That said, I'm not a Chromium extension dev and it could actually be a bug. Not sure about the implementation details.

My workaround was simply to install a custom new tab extension and replace the new tab page with my personal blog. Since it counts as a website and not an internal interface, the extension keeps working.

[ermismag]

I think this is a chrome/chromium limitation for security reasons, that a plugin can't access, chrome://newtab. That's why the plugin ships with it's own blank page.

Just set the plugin blank page as your new tab page or map it to the key you use to open blank tab:

map a :tabnew<CR>

or

map a :tabnew chrome-extension://ihlenndgcmojhcghmfjfneahoeklbjjh/pages/blank.html<CR>