- From: <bugzilla@jessica.w3.org>
- Date: Fri, 02 Mar 2012 10:19:30 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15904 --- Comment #2 from sun <sun@unleashedmind.com> 2012-03-02 10:19:27 UTC --- Further debugging by Dave Reid revealed that <input type="text" pattern="[0-9]/[0-9]" /> matches the string '0/0' even though the forward slash is not escaped. However, <input type="text" pattern="[0-9]\/[0-9]" /> *also* succeeds to match the string '0/0'. Hence, '/' does not seem to be the regular expression's delimiter (in some browser implementations). Testing this on http://html5pattern.com/#t=Expression%20delimiter&a=sun&d=1/1/1/1.1%5B1%5D1%5C%20and%201/1/121.1%5B1%5D1%5C%20might%20pass.%20The%20escape%20character%20seems%20to%20be%20%5C%2C%20but%20/%20is%20not%20the%20regex%20delimiter.%20What%27s%20the%20delimiter%3F&ta=&p=1/1%5C/1.1%5C.1%5C%5B1%5C%5D1%5C%5C seems to confirm that '/' is not the reserved expression delimiter. It also seems to confirm that '\' is the escape character. So the problem remains to be that we need to know what the expression delimiter is, in order to actually perform and ensure proper escaping of that character in the regular expression. See: http://stackoverflow.com/questions/9526814/what-is-a-safe-pcre-regex-delimiter-to-use-on-html5-pattern-input-element-attrib -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 2 March 2012 10:19:36 UTC