Skip to content

WindowOrWorkerGlobalScope should extend GlobalFetch #552

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghost opened this issue Aug 2, 2018 · 4 comments
Closed

WindowOrWorkerGlobalScope should extend GlobalFetch #552

ghost opened this issue Aug 2, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Aug 2, 2018

Since it redeclares fetch(input: RequestInfo, init?: RequestInit): Promise<Response>;.
Or GlobalFetch could be removed since it's only used as a supertype of Window which already implements WindowOrWorkerGlobalScope anyway.

@saschanaz
Copy link
Contributor

saschanaz commented Aug 2, 2018

GlobalFetch has been removed from the spec, so yes, it should be removed.

I'll submit a patch aftec #546 gets merged.

@mhegazy
Copy link
Contributor

mhegazy commented Aug 2, 2018

#546 will need some legal work too since it adds a new copyright notice, and we need to get MS lawyers to look at it. so it will take some time.

@saschanaz
Copy link
Contributor

GlobalFetch is not there anymore

@github-actions close

@github-actions
Copy link
Contributor

Closing because @saschanaz is one of the code-owners of this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants