Re: [whatwg/url] Setting a port on a URL that cannot have a username/password/port should return the set value (#330)

I take it you're referring to the `assert_equals` function defined in W3C's testharness.js?

I was under the impression that console output was the return value of an executed expression.

Tracing language-specific semantics is difficult, because it usually winds up back in ECMAScript, which itself has many layers of nested definitions of behavior. The way I've implemented it is for the setter to fall through to the getter code and return the value from that, unless explicitly told to return early. I guess that's incorrect?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/330#issuecomment-312550207