Closed GoogleCodeExporter closed 9 years ago
Since you know the codes well, can you provide a small standalone program
that we can reproduce the problem
Original comment by andrewch...@chromium.org
on 24 Nov 2014 at 10:53
Unfortunately, the page I see this on can not be made public, and I can't
reproduce it elsewhere.
I'm pretty sure it is an issue of the element moving in the DOM after lookup.
As I understand it, Chrome grabs the coordinates of the frame element after the
page load. If the frame element can not later be found at that location, when
we try to switch to it, it seems to be throwing a NoSuchFrameError. I'm
assuming it would just be a matter of checking if the element is stale before
attempting to switch to it.
Original comment by titusfor...@gmail.com
on 24 Nov 2014 at 11:13
can you send the page to me direct?
Original comment by andrewch...@chromium.org
on 2 Dec 2014 at 10:33
Unfortunately employee-only access, and I wasn't able to mock it out well
enough to reproduce it on its own. Sorry.
Original comment by titusfor...@gmail.com
on 2 Dec 2014 at 10:41
Original comment by andrewch...@chromium.org
on 30 Dec 2014 at 1:54
Original comment by samu...@chromium.org
on 21 Feb 2015 at 12:26
Original issue reported on code.google.com by
titusfor...@gmail.com
on 21 Oct 2014 at 6:28