Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial: fix confusing phrasing for opener setter #3916

Merged
merged 2 commits into from
Aug 15, 2018

Conversation

domenic
Copy link
Member

@domenic domenic commented Aug 14, 2018

Closes #3904.


/browsers.html ( diff )

@domenic domenic added the clarification Standard could be clearer label Aug 14, 2018
source Outdated
<code>Window</code> object, "<code data-x="">opener</code>", { [[Value]]: the given value,
[[Writable]]: true, [[Enumerable]]: true, [[Configurable]]: true }). Rethrow any
exceptions.</p></li>
<li><p>Perofrm <span>OrdinaryDefineOwnProperty</span>(this <code>Window</code> object, "<code
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perform

Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The combination of ECMAScript and HTML speak is a little weird, but I'm not sure I've a better idea. The main question that comes to mind is whether we should add a ? here.

@domenic
Copy link
Member Author

domenic commented Aug 15, 2018

I think that would be an alternative to "rethrow any exceptions", but we've mostly confined the usage of ?/! notation to larger algorithms which are explicitly called out as interfacing with the ES spec, whereas this is more of a one-off call into those mechanisms.

@domenic domenic merged commit fefb879 into master Aug 15, 2018
@domenic domenic deleted the fix-opener-setter-style branch August 15, 2018 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer
Development

Successfully merging this pull request may close these issues.

None yet

3 participants