Oh no. I now see two things.

1. There is overlap with PR Add WindowOrWorkerGlobalScope #416. I didn't even see it until I raised this PR.
2. I only added the properties and not the methods. (sigh)

Regarding the surface area of this PR that intersects with #416, this PR is more accurately typed. The only concern with this PR is that it is incomplete. We can either merge this first and then follow up with a revised #416, or combine this and #416 to form a new PR. @sjrd please let us know which you'll allow and we'll make it happen.

@exoego Happy to work together to combine our PRs, or if you couldn't be bothered anymore, I'm happy to integrate your PR into mine. Yours did come first after all :D よろしくお願いします

@japgolly I am fine if I close #416 and you make this PR complete by bringing some missing parts from #416 😄

np @exoego I'll combine our PRs in the next few days. 👍 And thanks for your work there. I've got so much other work to be doing so I think I'd cry if I myself had to write all the new facades in your PR 😅

I'll combine our PRs in the next few days

A few days, a month, they're the same thing right? Hmmm.... Moving on. I've merged #416 into this PR and made a few little fixes. This is good to go now.

@japgolly Could you update this PR so that @sjrd may review ?

Yeah I have already. I did on 15th Dec 2020. There's a comment right above yours @exoego 😄

Did a rebase.

For scalajs-dom 2.x, which doesn't have to support Scala.js 0.6.x, a much better alternative to defining WindowOrWorkerGlobalScope is to simply define its members as @js.native members of the dom package object. For example, like how fetch is defined in
https://github.com/scala-js/scala-js-dom/pull/458/files#diff-492b8ef836683ba613a558252a12fa68f30e3fd2a220fc21a1082a1d7319fe2e

@japgolly is this binary compatible? I don't think this change is:

CacheStorage moved into experiment.cachestorage as it's available from Window too

I think the rest would be okay though. So either undo just the CacheStorage change and merge or put off to 2.0?

@armanbilge Nah it's not. I'll update this soon (not today though) for compat.

Ready to go @armanbilge !

This is a huge one so I'm just going to check changes with bincompat implications and assume you got the facade types right and/or they can be fixed compatibly in the future.

Thanks @armanbilge ! 🚀

Thanks to you!! This was an important one :)

Do you think we might get 1.2 out today?

Ooooo do you want to? Are we ready? Anything else you want to add before we do? The only thing left on my list is to get #424 merged in for 1.2.0. I'm not sure if I'll get to it day though, feel free to take that one over if you want. Apart from the experimental question, I was also planning to just test arg = "UTF-8" instead of arg = js.native in something that actually runs and just see what happens.

@japgolly did you see my comment #424 (comment)? It's explained in the Scala.js docs (it's essentially equivalent to arg = js.native).

Ooooo do you want to? Are we ready? Anything else you want to add before we do?

I think so! The most important question for me is did we break anything, which I don't think so. If we forgot something or there are more nice-to-haves, theoretically we could do a 1.2.1 or 1.3 etc. I really really hope that getting a release out with all these merged PRs will encourage the community to become more engaged :)