Add test to ensure FileReaderSync isn't supported in service workers.

[mkruisselbrink]

This was removed from the spec in w3c/FileAPI#16.

[wpt-pr-bot]

Notifying @ehsan. (Learn how reviewing works.)

These tests will be available shortly on w3c-test.org.

• service-workers/service-worker/historical.https.html

[mkruisselbrink]

Possibly it makes more sense to add this to the FileAPI/historical.html test instead (and rename that to historical.https.html)...

[w3c-bots]

View the complete job log.

[w3c-bots]

View the complete job log.

Firefox (nightly channel)

Testing web-platform-tests at revision f64dd7e
Using browser at version BuildID 20170314110401; SourceStamp 6d38ad302429c98115c354d643e81987ecec5d3c
Starting 10 test iterations
All results were stable

All results

1 test ran

/FileAPI/historical.https.html

Subtest	Results	Messages
	OK
"toNativeLineEndings" should not be supported	PASS
"FileError" should not be supported	PASS
"FileException" should not be supported	PASS
Blob should not support slice prefixed	PASS
BlobBuilder should not be supported.	PASS
createFor method should not be supported	PASS
Blob.close() should not be supported	PASS
Service worker test setup	PASS
"FileReaderSync" should not be supported in service workers	FAIL	assert_false: expected false got true

[Ms2ger]

Possibly it makes more sense to add this to the FileAPI/historical.html test instead (and rename that to historical.https.html)...

Yes, I think so. Would you mind doing that?

[mkruisselbrink]

I'll make that change. One reason I didn't originally was that it seemed a bit weird to have a file API test fall for service workers not being implemented. But this test does really belong there.

[mkruisselbrink]

Okay, I moved the test to FileAPI/historical.https.html, but only run the service worker related tests if service workers are actually supported.

[w3c-bots]

These tests are now available on w3c-test.org

[mkruisselbrink]

@Ms2ger are you happy with the current status of this PR?