Monorail Project: chromedriver Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 14 users
Status: Available
Owner: ----

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment
testIFrameWithExtensionsSource is failing on Chrome v60+
Project Member Reported by, May 19 Back to list
ERROR: testIFrameWithExtensionsSource (__main__.ChromeExtensionsCapabilityTest)
Traceback (most recent call last):
  File "/b/build/slave/chromedriver_mac_10_6/build/src/chrome/test/chromedriver/test/", line 1848, in testIFrameWithExtensionsSource
  File "/b/build/slave/chromedriver_mac_10_6/build/src/chrome/test/chromedriver/test/../client/", line 307, in SwitchToFrame
    self.ExecuteCommand(Command.SWITCH_TO_FRAME, {'id': id_or_name})
  File "/b/build/slave/chromedriver_mac_10_6/build/src/chrome/test/chromedriver/test/../client/", line 274, in ExecuteCommand
    response = self._ExecuteCommand(command, params)
  File "/b/build/slave/chromedriver_mac_10_6/build/src/chrome/test/chromedriver/test/../client/", line 267, in _ExecuteCommand
    raise _ExceptionForLegacyResponse(response)
NoSuchFrame: no such frame: element is not a frame
  (Session info: chrome=60.0.3105.0)
  (Driver info: chromedriver=2.29.461585 (0be2cd95f834e9ee7c46bcc7cf405b483f5ae83b),platform=Mac OS X 10.12.2 x86_64)

This test was introduced in to fix  issue#1777  (background:  issue#1777  started failing on Chrome v58+ due to culprit CL ).

Bisecting to see what caused it to fail again on Chrome 60+ .

Project Member Comment 1 by, May 22
The following revision refers to this bug:

commit 571564116da46b3dcd202f9d03c3de41457a9f46
Author: gmanikpure <>
Date: Mon May 22 17:01:49 2017

[Chromedriver] Disable testIFrameWithExtensionsSource on HEAD.


Cr-Commit-Position: refs/heads/master@{#473603}


Project Member Comment 2 by, May 23
Performed bisect and found the culprit CL :

Looks like support for "--force-fieldtrials=SiteIsolationExtensions/Control" Chrome command line switch has been removed in this culprit CL. And hence, the fix no longer works for v60+.

Project Member Comment 3 by, May 23
From the logs, I see two differences :

1) DEVTOOLS EVENT Page.frameDetached is triggered.

2) DEVTOOLS EVENT DOM.setChildNodes doesn't have "frameId".

Attaching the verbose logs of fail run on v60 and pass run on v58.
20.3 KB View Download
35.2 KB View Download
Project Member Comment 4 by, May 25
Labels: Pri-1
Status: Available
Comment 5 by, Aug 16 (6 days ago)
some time no update. When it can be solved?

Sign in to add a comment