DevTools: Chrome VS Vivaldi are the very same?
I was starting to compare Chrome DevTools and Vivaldi DevTools. I'm using Chrome v.70.0.3538.110 (Official Build) (64-bit) and Vivaldi 2.1.1337.47 (Stable channel) (64-bit). (latest stable versions to date).
So at the very beginning of the getting started with DevTools, view an element's CSS tutorial, the first step guides the user to inspect an element called Inspect Me!.
Doing so with Chrome shows me the inspected element in the DOM Tree like this:
There it is... Now, I'd expect the same using Vivaldi, but this is what I got:
It doesn't even highlight the element...
Following the DOM tree that is given by Chrome, I try to get to the element in Vivaldi manually. Following all tags I get to the level where the Inspect Me! element is, but it's not there. In this screenshot I have Chrome to the left and Vivaldi to the right:
I know Vivaldi is based in Chromium but Chrome is essentially the same, isn't it?
Why this simple tutorial is not working as expected in Vivaldi?
Thanks in advace!!
Hadden89 last edited by Hadden89
If you notice difference in codes could be due different user agent (the site content may change with different browser strings), extensions which are on V and not on chrom* and, sometimes, a bug (in such case report what you discover).
I get the same message,
During such test, is always suggested to disable extensions, or use a copy without any extension on it (for closest results).
@hadden89 I understand what you say, but I tested it... I know my previous screenshot doesn't reflect this and I didn't mention it (sorry), but I do test this in Incognito windows in each browser. That means no extensions were enabled because none of them in any of the browsers have permissions to be allowed in Incognito (I verified manually each one of them to be absolutely sure). By doing so, the described behavior remains...
What else can I test? Why in this example both browsers don't get the same expected result?
Thanks again for reading.
@Hadden89 in this case it seems to be DevTools inability to inspect out-of-process iframes.
Reproduced with extensions disabled on
2.2.1369.6, different platforms.
@metafaniel could you check
iframeprocess state in Chrome to compare DevTools capabilities?
Chrome might uses a (different) whitelist to what it considers same domain or maybe has the opt-out state by default for now.
For Vivaldi the
#site-isolation-trial-opt-outneeds to manually be set to the (not recommended) Opt-out value to get inspection on that site to work correctly (for now).
Otherwise the frames are confined in a separate subframe process for
iframequery is redirected to that (external) domain (also when using
So another posiblility would be Google using user agent sniffing to serve a "locally" hosted version for Chrome only.
Kill that process (
Esc) to see the dead bird for affected sections of that page.
@becm Hi, thanks: that seems to be the case.
So Chrome and Vivaldi iframe process appears as:
Incognito Subframe: https://google-developers.appspot.com/
Killing the process as suggested makes appear as many sad faces in Chrome as dead birds in Vivaldi.
#site-isolation-trial-opt-outmakes the inspection work as expected and makes this Incognito Subframe process disappear, of course. You did it!!
But now what? Is that a good thing, a bad thing or is it neutral?
@metafaniel definitely a bad thing. Reproduced it with out-of-the-box profile to make sure it's not one of our "paranoid" non-standard config options.
If both browsers use subframe processes and only Chrome can (correctly) inspect in those conditions:
Either Vivaldi DevTools lack the (actual) ability to access subframe processes or there might be some config magic (possibly in this case via
I'd say it's a bug, unless somebody else has (or can ping someone with) deeper knowledge of what's (not) happening here exactly?
It is a bug.
Works in Chrome 71 but not Snapshot 2.2.
@metafaniel You should report it. I will confirm it if you poste the VB-XXXX number of the reported bug here.
Please read how to Report a bug for Vivaldi carefully and then report the bug to Vivaldi bugtracker.
metafaniel last edited by metafaniel
@metafaniel definitely a bad thing. (...)
It is a bug. (...)
That seemed to be the case, I just wanted to be completely certain. Thanks guys!
(...) @metafaniel You should report it. I will confirm it if you poste the VB-XXXX number of the reported bug here. (...)
Your bug report has been given the issue reference VB-46458
It's done folks. Thanks for your support!
The solution to set the flag
#site-isolation-trial-opt-outwon't work after the update to 2.5. When the flag is disabled, many extensions will crash, for example uBlock Origin, Adguard and the User-Agend Switcher (to get whatsapp web running). Also PDF files seem to be affected. If I try to open one, it will not render.
In the last stable version (2.4) everything worked fine.
Did anyone find a workaround for this?
@kr1styan Thanks for your investigation! Helpful!
I can confirm Disabling vivaldi://flags#site-isolation-trial-opt-out let frame inspection work in devtools but break many extensions.
I updated the bug entry for VB-46458.