It's seems you could always get the associated Document from the settings object's global object instead.
An alternative might be defining "relevant document" and using that throughout.
This came up in https://github.com/whatwg/html/pull/4214/files#r253238258.
This seems worthwhile as currently one of the requirements on BroadcastChannel's settings object reads "a global object that is a Window object and a responsible document that is fully active" which might make one think the Window object's associated Document is something else.
(This is a rather good issue if you're already somewhat familiar with the HTML Standard and are interested in streamlining language and potentially introducing new concepts that can be used across all the various standards that build upon HTML.)
It's seems you could always get the associated Document from the settings object's global object instead.
An alternative might be defining "relevant document" and using that throughout.
This came up in https://github.com/whatwg/html/pull/4214/files#r253238258.
This seems worthwhile as currently one of the requirements on
BroadcastChannel's settings object reads "a global object that is a Window object and a responsible document that is fully active" which might make one think the Window object's associated Document is something else.(This is a rather good issue if you're already somewhat familiar with the HTML Standard and are interested in streamlining language and potentially introducing new concepts that can be used across all the various standards that build upon HTML.)