- From: Jungkee Song <jungkee.song@samsung.com>
- Date: Thu, 16 May 2013 17:33:04 +0900
- To: hallvord@opera.com, WebApps WG <public-webapps@w3.org>
Hi Hallvord, While reviewing https://critic.hoppipolla.co.uk/r/86, I found the changed version assumes not firing readystatechange for the subsequent open() calls where the readyState is already 1, which in my understanding is not conformed to the current spec text. Commits are specifically: https://critic.hoppipolla.co.uk/a526c904?review=86 https://critic.hoppipolla.co.uk/89cc3591?review=86 I'll submit relevant issue comments right in Critics but in general do you see any issue with the readystatechange behavior with consecutive open() calls in the current spec text? Current browser implementations show: - Firefox fires. - Chrome and Opera do not. Jungkee Jungkee Song Samsung Electronics
Received on Thursday, 16 May 2013 08:33:33 UTC