26915 2014-09-27 10:08:48 +0000 Opt-in to the ES6 `u` flag for regular expressions? 2014-10-10 20:38:40 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED https://html.spec.whatwg.org/#the-pattern-attribute P3 normal Unsorted 1 contributor ian ian mathias mike zcorpan contributor oldest_to_newest 112337 0 contributor 2014-09-27 10:08:48 +0000 Specification: https://html.spec.whatwg.org/multipage/forms.html Multipage: https://html.spec.whatwg.org/multipage/#the-pattern-attribute Complete: https://html.spec.whatwg.org/#the-pattern-attribute Referrer: https://www.google.com/ Comment: Opt-in to the ES6 `u` flag for regular expressions? Posted from: 176.219.173.4 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.58 Safari/537.36 OPR/25.0.1614.18 (Edition beta) 112338 1 mathias 2014-09-27 10:11:52 +0000 ES6 introduces the `u` flag for regular expressions, which makes their behavior much more sensible and Unicode-friendly. It would be nice to enable this flag for the `pattern` attribute. Backwards compatibility is a concern (I’ve documented some differences in behavior here: https://mathiasbynens.be/notes/es6-unicode-regex) so we might need a new opt-in switch. 112392 2 ian 2014-09-29 16:36:20 +0000 Isn't there an inline opt-in like in Perl? (e.g. so you can have subregions that are case-insensitive and subregions that aren't?) 112413 3 zcorpan 2014-09-29 20:41:19 +0000 Use counter for pattern: http://www.chromestatus.com/metrics/feature/timeline/popularity/44 Earlier discussion about `i`: https://www.w3.org/Bugs/Public/show_bug.cgi?id=11011 112972 4 ian 2014-10-10 20:38:40 +0000 I think if we have to have an out-of-band opt-in, this is a non-starter. However, if we can just turn this on always, it would make a lot of sense. I've gone ahead and made "u" be specified always. Hopefully this is Web-compatible. The biggest risk is with inappropriate escapes (as in pattern="\a").