Last modified: 2013-12-02 14:22:11 UTC
There is a mw.uri test which fails in Internet Explorer 8: Testname: basic object properties Expected: { "fragment": undefined, "host": "www.ietf.org", "path": "/rfc/rfc2396.txt", "port": undefined, "protocol": "http", "query": {} } Result: { "fragment": "", "host": "www.ietf.org", "path": "/rfc/rfc2396.txt", "port": "", "protocol": "http", "query": {} } Testname: Parse an ftp URI correctly with user and password Expected: { "fragment": undefined, "host": "192.0.2.16", "password": "pwd", "path": "/", "port": undefined, "protocol": "ftp", "query": {}, "user": "usr" } Result: { "fragment": "", "host": "192.0.2.16", "password": "pwd", "path": "/", "port": "", "protocol": "ftp", "query": {}, "user": "usr" } and some more (6 failures) Looks like InternetExplorer init all capturing groups with a empty string and when the group not matched the empty string is the value.
http://xregexp.com/cross_browser/#npcgUndefined In Internet Explorer, captured values for nonparticipating capturing groups are incorrectly returned by RegExp.prototype.exec and String.prototype.match as an empty string rather than undefined, making it impossible to determine group participation. Firefox splices empty strings instead of undefined into the array returned by String.prototype.split as the result of nonparticipating capturing groups.
