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 19573 - WebWorkers would be more flexible, if WorkerGlobalScope would not be readonly(e.g. wrapping the self object)
Summary: WebWorkers would be more flexible, if WorkerGlobalScope would not be readonly...
Status: RESOLVED NEEDSINFO
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: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-17 09:03 UTC by contributor
Modified: 2013-06-03 19:55 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-10-17 09:03:09 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html
Multipage: http://www.whatwg.org/C#the-global-scope
Complete: http://www.whatwg.org/c#the-global-scope

Comment:
WebWorkers would be more flexible, if WorkerGlobalScope would not be
readonly(e.g. wrapping the self object)

Posted from: 90.146.74.58
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4
Comment 1 Ian 'Hixie' Hickson 2013-01-26 00:57:16 UTC 
Can you elaborate?
Comment 2 myfacebook 2013-03-06 07:36:16 UTC 
It greatly enhances the possibilities for browser analytics, if WorkerGlobalScope can be replaced with a Wrapper.
I am not quite sure, why the WorkerGlobalScope should be readonly anyways. Is this to prevent the code from "accidently" overwriting the self object? Or is there any security concern?
Comment 3 Ian 'Hixie' Hickson 2013-04-12 22:40:30 UTC 
What do you mean by "readonly"?

Can you give an example of the code you wish to write that you can't write?