- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Jun 2014 10:26:23 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25958
Bug ID: 25958
Summary: TypeError or SyntaxError for querySelector() and
querySelectorAll()
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: DOM
Assignee: annevk@annevk.nl
Reporter: crimsteam@gmail.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
If matches() was changed:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24028
then what about querySelector() and querySelectorAll()? This methods are older
than matches(), but still in "scope-match a selectors string " algo we have:
2. If s is failure, throw a JavaScript TypeError.
Firefox, Chrome and IE return DOMException "SyntaxError", not JavaScript
TypeError (query() and queryAll() still not supported so skipping them). This
behaviour is correct per Selectors API Level 1/Selectors API Level 2:
http://www.w3.org/TR/selectors-api/#parse-a-selector
http://dev.w3.org/2006/webapi/selectors-api2/#parse-a-selector
so really any implementators wants/plans change this?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 June 2014 10:26:24 UTC