Regex test()
is giving me issues in Firefox and Chrome, yet it works flawlessly in开发者_运维问答 Opera and Safari.
troubled code:
var pattern = /(\s+(?!\$\w+)|(^(?!\$\w+)))/g;
if(pattern.test(String(id).replace(/\s+OR|AND\s+/g, ''))) {
searchError("You suck.");
return 1;
}
When you pass in white space, it blocks it every time. When you pass in something like '$a b'
then it will work every other time in Firefox/Chrome. WEIRD.
It's a bug in the RegEx engine, a similar question with the same issue came up here.
From my answer to that question: It's a bug with the way regexes are implemented in ECMAScript 3, there's a great post on the details here.
The basics are a /regex/
with the g
modifier doesn't reset correctly, so multiple .test()
calls alternate between true
and false
if everyone should be true
, every other calls successfully resets it.
This seems to still be an issue in August of 2021... I just want to share some things I have learned before stumbling upon this question and answer. I was baffled by this problem and had no meaningful way forward - until now.
It doesn't matter whether you use
exec()
ortest()
ormatch()
. The regex still doesn't work properly on every other occurrence.It doesn't matter if you set the regex with
let reg = new RegExp(/<table(\s*[^>]*)>/g);
or with const
. Doesn't matter if you set it globally or locally either...
What does work to bypass this problem is wrapping your regex statement in parenthesis in your loop like so:
Object.keys(table).forEach(key => {
if((new RegExp(/<table(\s*[^>]*)>/g)).test(___your test string___)){
//Do what you need to do
}
});
Remove the parenthesis around the Regex, and watch every other one fail....
Thank you so much for the answer @Nick Craver and the comment @prototype!
This exact Regex was what was giving me trouble. It would work for one object, and fail for the subsequent object, and it made no sense. I am only here to say that this is still very relevant in 2021.
精彩评论