Closed Bug 935165 Opened 12 years ago Closed 11 years ago

Make {encode, decode}{URI, URIComponent} available on Chrome Workers

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: Yoric, Assigned: jorendorff)

References

Details

According to the documentation, we don't have these functions. I don't see any good reason to not have them.
This is a js builtin, so I suspect it's caused by us not calling JS_InitStandardClasses on workers. It doesn't look like these are hooked up to JS_ResolveStandardClass ... I claim this is a JS bug.
Component: DOM: Workers → JavaScript Engine
Depends on: 934889
Definitely a JS engine bug.
Does the JS team have any plans to pick up this (or, alternatively, bug 934889) in the near future?
Flags: needinfo?(cpeterson)
Sure, I'll take it.
Assignee: nobody → jorendorff
Hmm. "encodeURI" is hooked up to both JS_InitStandardClasses and JS_ResolveStandardClass. Does this reproduce now?
Flags: needinfo?(dteller)
If this bug is fixed, someone should verify whether Intl API bug 934889 is still reproducible.
Flags: needinfo?(cpeterson)
Looks good, this seems to have been fixed at some point.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dteller)
Keywords: dev-doc-needed
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.