Bug 27631
| Summary: | WorkerContext does not expose the right set of constructors | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrew Wilson <atwilson> |
| Component: | WebCore JavaScript | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | annevk, ap, ian, ukai |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Andrew Wilson
Section 5.4 of the worker spec specifies that the following list of constructors are the only ones that should be exposed to WorkerContexts:
XMLHttpRequest and all interface objects and constructors defined by the XMLHttpRequest specifications, except that the document response entity body must always be null. [XHR]
The WebSocket interface object and constructor. [WEBSOCKET]
The EventSource interface object and constructor. [EVENTSOURCE]
The MessageChannel interface object and constructor. [HTML5]
The Worker() and SharedWorker(url) constructors.
We currently don't expose EventSource, but do expose other things like MessageEvent and WorkerLocation.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
It's not clear why WorkerLocation is not exposed per the spec.
Andrew Wilson
For that matter, what about other things visible to workers, like ApplicationCache?
Andrew Wilson
From my email conversation with ianh:
> 1) What are the criteria used to determine the list of visible constructors
> in section 5.4 of the worker spec?
What I felt like adding that nobody complained about. :-)
So it seems that the list is somewhat arbitrary. If we want to add more things, we should pursue this on the whatwg list.
Fumitoshi Ukai
Sorry, closed different bug
Anne van Kesteren
This has been sorted out.