Closed Bug 1158347 Opened 9 years ago Closed 9 years ago

wpt testharness.js should use ServiceWorker.postMessage() instead of MessageChannel

Categories

(Testing :: web-platform-tests, defect)

Product:
Testing
Component:
web-platform-tests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bkelly, Assigned: bkelly)

References

(
URL
)

Details

Currently the wpt resources/testharness.js file uses MessageChannel for communicating errors back from ServiceWorkers.  This is an accommodation for early blink implementation issues.  However, the use of MessageChannel produces problems for gecko.

I think it would be best for everyone if the ServiceWorker tests just used ServiceWorker.postMessage() as its a part of the spec under test.
This is made more difficult by the current cache-storage/serviceworker tests running in the 'installing' state.  There are no controlled documents in this state, so we can't use Client to postMessage() back to the window.
Actually, we don't need a controlled document because we can just use MessageChannel.source from within the ServiceWorker.
Assignee: nobody → bkelly
URL: https://critic.hoppipolla.co.uk/r/4842
Status: NEW → ASSIGNED
The upstream changes have merged in bug 1161535, but we still need to re-enable these tests.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Depends on: 1161759
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.