Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pattern too long for this browser #24

Closed
GoogleCodeExporter opened this issue Nov 25, 2015 · 3 comments
Closed

Pattern too long for this browser #24

GoogleCodeExporter opened this issue Nov 25, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

 I attached a JS file which reproduces the problem.

What is the expected output? What do you see instead?

 Error: Pattern too long for this browser. 

What version of the product are you using? On what operating system?
 javascript running on Rhino, java 1.5

Please provide any additional information below.
 the patch causing that problem is created by patch_fromText() and a
subsequent reverting of the patch (changing DELETES into INSERTS - that's
why the first status field says "-0").

Original issue reported on code.google.com by simon.ob...@gmail.com on 7 Sep 2009 at 11:26

Attachments:

@GoogleCodeExporter
Copy link
Author

Works for me.  Attached is an HTML file which executes your code and prints the 
result.  No error is thrown in Firefox, Chrome, Safari, Opera and even IE.  
Sounds 
like a bug in Rhino?  I'm afraid I don't have a copy of Rhino installed to test 
right 
now.

The first thing I'd try is remove the umlauted characters from the input string 
and 
see if that's what's causing issues.

Are you able to run the unit tests in Rhino?  If so, that should at least tell 
you 
which function is kaput.

Original comment by neil.fra...@gmail.com on 7 Sep 2009 at 12:17

Attachments:

@GoogleCodeExporter
Copy link
Author

the bug doesn't appear with trunk HEAD. sorry, should have checked that first.

FWIW all unit tests pass in rhino (

Original comment by simon.ob...@gmail.com on 7 Sep 2009 at 12:33

@GoogleCodeExporter
Copy link
Author

No problem.

In that case it's a bug which was reported and fixed in December of last year.

Original comment by neil.fra...@gmail.com on 7 Sep 2009 at 12:45

  • Changed state: Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant