[Webkit-unassigned] [Bug 119508] Explicitly test same/cross-origin importScripts() effect on worker.onerror

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=119508





--- Comment #1 from Oliver Hunt <oliver at apple.com>  2013-08-05 20:01:40 PST ---
(In reply to comment #0)
> Consider merging tests added in https://chromium.googlesource.com/chromium/blink/+/94edc6173e6605b221187d62bccf2f77d2a7818c
> 
> We currently have a single test that checks behavior when calling
> importScripts() on a URL that redirects from same-origin to cross-origin.
> This patch adds tests for cross-origin and same-origin scripts, and updates
> the tests to use js-test-pre.js.
> 
> Currently we have some weird behavior for cross-origin scripts. The
> message is sanitized, the URL is set to the worker JS file, and the line
> number is the call to 'importScripts'.
> 
> Firefox has different weird behavior: the message is unsanitized, but
> the URL and line number are emptied.
> 
> I think it's reasonable to leave the expectations as they are, but our
> eventual goal should be to sanitize these errors in the same way that we
> do normal cross-origin messages.

The reason for cross origin sanitization in the normal case is that <script> allows cross  origin loads, workers don't (sans the CORS bits)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.