Change Decode!jsstr.cpp to conform to latest ES5 drafts

RESOLVED WORKSFORME

Status

()

Core
JavaScript Engine
RESOLVED WORKSFORME
9 years ago
6 years ago

People

(Reporter: Waldo, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
Most particularly at a glance, I suspect ES3 allowed a percent sequence starting with an encoded octet with 5 or 6 upper bits set because Unicode allowed this at the time, but modern Unicode allows at most 4 upper bits to be set, and ES5 makes >4 an error (assuming it isn't already -- if it is, SpiderMonkey's current algorithm obscures it more than ES5's algorithm does).
(Reporter)

Comment 1

6 years ago
Fixed at some point, jsstr.cpp's Decode now has |goto report_bad_uri;| if |n > 4|.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.