This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28411 - Base URL for importScripts doesn't appear to be defined
Summary: Base URL for importScripts doesn't appear to be defined
Status: VERIFIED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#importi...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-06 14:27 UTC by contributor
Modified: 2015-09-16 08:11 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2015-04-06 14:27:34 UTC 
Specification: https://html.spec.whatwg.org/multipage/workers.html
Multipage: https://html.spec.whatwg.org/multipage/#importing-scripts-and-libraries
Complete: https://html.spec.whatwg.org/#importing-scripts-and-libraries
Referrer: https://html.spec.whatwg.org/multipage/

Comment:
Base URL for importScripts doesn't appear to be defined

Posted from: 84.197.6.214 by ms2ger@gmail.com
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0
Comment 1 Ms2ger 2015-04-06 14:28:26 UTC 
There is no explicit base URL passed, so "let base be the element's base URL." applies. There is no element, though.
Comment 2 Ian 'Hixie' Hickson 2015-04-07 22:58:50 UTC 
The spec says:

| If the URL came from a script (e.g. as an argument to a method)
|   The URL character encoding is the API URL character encoding specified
|   by the script's settings object.

Is that insufficient? I'm confused.
Comment 3 Ms2ger 2015-04-08 08:13:04 UTC 
"character encoding" != "base URL"
Comment 4 Ian 'Hixie' Hickson 2015-04-09 19:13:06 UTC 
Oh duh. Sorry. My bad. Yeah, it should always pass the base URL.
Comment 5 Anne 2015-09-15 14:49:36 UTC 
https://github.com/whatwg/html/pull/145
Comment 6 Ms2ger 2015-09-16 08:11:12 UTC 
Thanks!