Use current settings object instead of relevant settings object

[zcorpan]

https://websockets.spec.whatwg.org/#dom-websocket-websocket says

Let client be this's relevant settings object.

client is used for base URL for parsing relative URLs. This was introduced in #45

I think "relevant" should be "current". See web-platform-tests/wpt#39978 (comment)

WebSocket spec says to use the relevant settings object, but going by the example in https://html.spec.whatwg.org/multipage/webappapis.html#realms-settings-objects-global-objects there's no way to test for the relevant settings object for a constructor (vs a method), since you can't use .call() with a constructor.

I used current instead, like Workers, but this needs a spec change.

[domenic]

Inside constructors, "this's relevant settings object" === "current settings object", because of how "this" is constructed. So both are correct.

[zcorpan]

OK. Can we have a note to that effect?

[domenic]

I'm not sure we need to add that to every spec that uses constructors, but maybe we could add it around https://html.spec.whatwg.org/#concept-relevant-everything ?

[zcorpan]

Yeah, good point. I'll open an issue for html.