- From: Andreas Tolfsen <ato@mozilla.com>
- Date: Thu, 5 Mar 2015 09:18:44 +0100
- To: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
On 3 Mar 2015, at 18:49, James Graham <james@hoppipolla.co.uk> wrote:
> The other situation is
>
> POST /session/{sessionId}/element/{ELEMENT}/element
>
> with a body like
>
> {"using": "css selector", value:"some selector"}
>
> Where {ELEMENT} is a real element, but the selector doesn't match
> anything. This clearly isn't a 404 error (maybe a 500; I'm not sure what
> makes 501 appropriate here). However it is still a "no such element"
> error in the spec.
Why doesn't 404 make sense here? It's a child element lookup for the descendants of ELEMENT. If ELEMENT is #a and the selector .foo, it's no different to the expression #a > .foo.
Received on Thursday, 5 March 2015 08:19:15 UTC