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 27143 - There's no reason to set a "responsible browsing context" since it is never used. Not having it for [...]
Summary: There's no reason to set a "responsible browsing context" since it is never u...
Status: RESOLVED INVALID
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/#script-...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-23 15:54 UTC by contributor
Modified: 2016-03-28 13:19 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-10-23 15:54:30 UTC 
Specification: https://html.spec.whatwg.org/multipage/workers.html
Multipage: https://html.spec.whatwg.org/multipage/#script-settings-for-workers
Complete: https://html.spec.whatwg.org/#script-settings-for-workers
Referrer: 

Comment:
There's no reason to set a "responsible browsing context" since it is never
used. Not having it for workers seems better as service workers definitely
cannot have it and people already write algorithms on top of "environment
settings object" assuming this thing is always there.

Posted from: 46.127.136.57 by annevk@annevk.nl
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:36.0) Gecko/20100101 Firefox/36.0
Comment 1 Ian 'Hixie' Hickson 2014-10-23 17:25:55 UTC 
I assume you mean just for workers, right?
Comment 2 Anne 2014-10-23 18:14:20 UTC 
Yes.
Comment 3 Ian 'Hixie' Hickson 2014-11-26 22:21:23 UTC 
When you turn off scripting for a browsing context, should workers also stop?
Looks like right now that's the only thing the Worker responsible browsing context is used for.
Comment 4 Anne 2014-11-27 08:11:44 UTC 
I think "disable scripting" if such a setting still makes sense this day and age should not be tied to a browsing context. That would not work for a service worker for instance.
Comment 5 Ian 'Hixie' Hickson 2014-11-29 00:26:24 UTC 
Well what's the UI for turning off scripting going to be? The only UI I'm aware of these days is at the browsing context level.
Comment 6 Anne 2014-11-29 15:37:10 UTC 
I would imagine we're going to a world of per-origin preferences. So you can manage notifications, storage, etc. Perhaps disable scripting can be there too, if UAs are still interested in supporting that use case without extension.
Comment 7 Anne 2016-03-28 13:19:25 UTC 
No longer convinced this makes sense. We probably still need to make changes, but workers keeping some kind of link to their owner is likely important for SharedArrayBuffer.