Closed Bug 487010 Opened 16 years ago Closed 6 years ago

Add option to allow unicode format-control characters

Categories

(Rhino Graveyard :: Core, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: mguillemot, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032711 Ubuntu/8.04 (hardy) Firefox/3.0.8 Build Identifier: Section 7.1 of ECMA definition is clear concerning unicode format-control characters: ----------------------- "... These characters are removed from the source text before applying the lexical grammar. Since these characters are removed before processing string and regular expression literals, one must use a. Unicode escape sequence (see 7.6) to include a Unicode format-control character inside a string or regular expression literal." ----------------------- And this is verified by standard test ecma_3/Unicode/uc-001.js which (approximatively) tests that: "no error" === eval('"no\u200E error"') The problem for HtmlUnit is that none of the "normal" browsers respect that and all accept unicode format-control characters. The consequence is that we would need a possibility to configure Rhino to consider these characters as normal characters rather than to dismiss them. What would be the best way for that? Once this is defined, I can provide a patch. Reproducible: Always

Closing. Bug management is now done here:
https://github.com/mozilla/rhino

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.