29218 2015-10-21 14:48:31 +0000 Order of error checks in spec incompatible with proxy implementations 2015-10-31 03:22:28 +0000 1 1 1 Unclassified Browser Test/Tools WG WebDriver unspecified PC Linux NEW P2 normal --- 20860 1 james public-browser-tools-testing ato mike public-browser-tools-testing oldest_to_newest 123823 0 james 2015-10-21 14:48:31 +0000 "1. If the current browsing context is no longer open, return error with error code no such window. 2. Handle any user prompts, and return its value if it is an error. 3. Let cookie be the result of getting a property named "cookie" from the parameters argument." This pattern doesn't work with a proxy implementation since it must read the full request before communicating with the backend that can know things like whether the browsing context is still open. Also the browsing context may close whilst the request is being read. So generally it seems better to delay these checks until after the request is fully processed. 124019 1 ato 2015-10-31 03:22:28 +0000 By “proxy implementation” I’m assuming you mean “intermediary node”. You say that they need to read the full request before communicating with the backend. I guess I don’t understand what this means, since intermediaries won’t run any of the remote end steps themselves. They act, as you say, as proxies, or multiplexers.