Vimium: Cancelled requests for vomnibar.html in Developer Tools

[vvs]

For every URL visit in Chrome, I see a red (cancelled) request to vomnibar.html, listed in the Chrome Developer Tools, in the Network tab.

Url: chrome-extension://dbepggeogbaibhgnhhndojpepiihcmeb/pages/vomnibar.html
Method: GET
Status: (Cancelled)
Initiatior: ui_component.js:46
Size: 0B
Time: 106 ms

It would be nice to eliminate this noise from the dev tools, esp. in those cases when I don't use vomnibar at all.

[smblott-github]

I cannot reproduce that, @vvs...

This is on a bare-minimum blank page, but it's similar on more complicated pages, including those with frames.

[vvs]

Weird. That's what I see on Chrome 59.0.3071.86 (Official Build) (64-bit), with only single extension enabled (vimium, naturally).

[philc]

I also see one blocked vomnibar request per page load in the network tab,
although the vomnibar works fine. This is occurring on chrome 58.0.3029.110.

On Thu, Jun 8, 2017 at 12:27 AM, Vladimir Sizikov [e-mail]
wrote:

Weird. That's what I see on Chrome 59.0.3071.86 (Official Build) (64-bit),
with only single extension enabled (vimium, naturally).
[image: vomnibar]
https://user-images.githubusercontent.com/9781/26916989-b78a56ec-4c2c-11e7-850e-7a8cf865bae3.png

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/philc/vimium/issues/2534#issuecomment-307022546, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAhlk_iCgL8Zyq6OKhSGtLPqP6I6O1-ks5sB6J5gaJpZM4NzGqX
.

[gdh1995]

This "cancelled" request occurs since Chrome about 56, and I think, is because Chrome move vomnibar.html into an single assistant process to render it since Chrome 56. Here's my guess:

• Chrome sends a request of vomnibar.html in the main process which rendering the top frame
• It finds vomnibar.html should be moved into another process
• It cancelled the request (and logs this action)
• Another process (it may be created newly) loads and renders vomnibar.html and pass the canvas to the main process.

This is just like effects after enabling the flag "#enable-site-per-process", but is always on since Chrome 56. I haven't found any way to avoid it. So maybe we need to create an issue on the Chromium forum.

[uudiin]

A frame named vomnibar.html is showed in Element tab, How to eliminate this noise from the dev tools?
Thank you

[gdh1995]

@uudiin Sorry but it's impossible to hide Vimium's elements, up to now. Unlike what's in Firefox, Vimium++ needs to operator the page's DOM tree on Chrome to show its link hints and Vomnibar.