Bugzilla

> Reading the specification today I've found this passage:

> To get a known element with argument reference, run the following steps:

> Let element be the item in the current browsing context’s list of known elements for which the web element reference is equal to reference, if such an element exists. Otherwise return error with error code no such element.
This implies that if we pass an ID of an element that does not belong to the current context the driver should return "no such element" error and the current behavior is correct. The referenced element is not stale. It just belongs to another context and it can be used if we switch to its context.

>So it must be a broken test, not a regression. And also there must be a bug in other drivers.

I think that is the wrong section?  

More correct would be

"
To get a known connected element with argument reference, run the following steps:

Let element be the result of trying to get a known element with argument reference.
If element is not connected return error with error code stale element reference.
Return success with element.
"

given we know the element was connected (we have a reference) we should be falling into the above no?
if not then why is there a section about the element not being connected for something that is known connected?

removed this comment as I think it was referring to something else.