Skip to main content

Is handling of curly braces in javascript regex is the same across all modern browsers?


Curly braces in JavaScript regex is used to denote quantifiers. So writing




a{2,4}



will match aa, aaa and aaaa. But if you mistype this quantifier like this:




x{1,x}



It will match the literal text "x{1,x}", at least in Firefox.



Is this behavior common to modern browsers?



The ECMA standard prohibits this behavior and requires the escaping of the braces.



(Background: I have to write a parser for javascript regexes at work.)


Source: Tips4allCCNA FINAL EXAM

Comments

  1. I don't know for JavaScript and browsers, but this is the behaviour I would have expected and that I have seen in the past in regular expressions.

    So I tested different regex engines on their behaviour:


    C#: behaves this way
    Perl: behaves this way
    Python: behaves this way
    PHP: behaves this way
    Java: throws an Exception

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex