returning false when calling test() multiple times

[cybernetics]

returning false for the given example test on Firefox Nightly (v30) & Chrome 32.0.1700.107

[cybernetics]

[cybernetics]

but when the generated regex is being validated with some other tools, it's returning true for both example test cases, see below.

[mihai-vlc]

Thank you for your screens this was already reported and discussed in #63
remove the g modifier and it will work as expected

[cybernetics]

as per http://blog.stevenlevithan.com/archives/es3-regexes-broken
this bug was in ES3 and expected to get fixed in ES4. the above screens are running latest firefox & chrome and I believe both support ES 5.1 spec. I think this library should take care of this nasty bug, and do not force the end user to think for tweaks, if not yet fixed in todays latest browsers.

thnx for the input.

[cybernetics]

this library is supposed to provide the abstractions for the low level regex intricacies.

[mihai-vlc]

Well this is more then an year old but you know what they say better late then never 😄 .

This is the expected behavior for a regex with the g flag.
When test() is called on a regular expression with the g flag it sets the lastIndex property of the regular expression object to the character position immediately following the matched sub-string.
When we call it the second time it begins the search from the specified lastIndex. If no match is found it will return false and the lastIndex property is set back to 0.

Here we have some code to better understand this:

var reg = /fn/g;
reg.test('hello') // => false
reg.lastIndex // => 0
reg.test('some fn text') // => true
reg.lastIndex // => 7
reg.test('some fn text') // => false
reg.lastIndex // => 0
reg.test('some fn text fn me me') // => true
reg.test('some fn text fn me me') // => true
reg.test('some fn text fn me me') // => false

If you need to prevent this you can set the lastIndex property back to 0 at any time.

MDN RegExp.lastIndex.

[mihai-vlc]

Closing this one as this is the expected behavior.