Window/isSecureContext→WindowOrWorkerGlobalScope/isSecureContext, and update spec URL

[sideshowbarker]

Fixes #1192

[domenic]

It still seems a bit weird that the page URL is Window/isSecureContext and it talks about the window.isSecureContext API. I'd have expected it to be more like https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/origin

[sideshowbarker]

It still seems a bit weird that the page URL is Window/isSecureContext and it talks about the window.isSecureContext API. I'd have expected it to be more like developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/origin

Good point. I’ll update the patch to move it (along with adding a redirect) — and also change it in the body of the article.

[sideshowbarker]

Well it turns out we do already have https://developer.mozilla.org/en-US/docs/Web/API/WindowOrWorkerGlobalScope/isSecureContext — so I’ll make the updates there instead, and just change https://developer.mozilla.org/en-US/docs/Web/API/Window/isSecureContext to a redirect to that.

[sideshowbarker]

@domenic updates pushed — please re-review

[sideshowbarker]

@domenic friendly ping

[domenic]

Perfect, thank you!!

[sideshowbarker]

@jpmedley, @chrisdavidmills This is an easy review that’s already gotten a domain-expert OK but I guess hadn’t been merged yet just due to having merge conflicts. I resolved the conflicts, so it should now be ready for review/merging

[chrisdavidmills]

The trouble I have with this PR is that @Elchi3 is currently working on removing all mixin content from MDN, and instead creating pages hanging off the the objects that the mixin-defined properties are actually access from, as it will be a lot less confusing for readers.

So Florian, is this change helpful in terms of housekeeping for the mixing work, or should we leave this page where it is?

[Elchi3]

Thanks for the ping, Chris!

Yeah, so the current idea is to get rid of WindowOrWorkerGlobalScope and other mixin friends because these aren't real things to web developers. Please read more about it at #1940 (feedback welcome)

WindowOrWorkerGlobalScope is a bit special so we've started thinking about it here: #2427

I think this PR should be closed as it will be solved with #2427

[sideshowbarker]

OK, closing per #1228 (comment)