-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Remove redundant call to nearest open popover #9267
Conversation
FYI I just removed the assert which I thought was ok to add, candidate can still be null. |
Do we need to add back the early return since the candidate can still be null? |
Passing a null candidate to the subsequent call to nearest open popover is acceptable. @mfreed7 intentionally removed the early return and said so here: https://chromium-review.googlesource.com/c/chromium/src/+/4514422
|
A Chromium commit isn't proof that it works in the standard though. If you look at the algorithm it expects a node and doesn't allow for null to be passed. |
@josepharhar I'm going through the popover issues, I think this is close to being mergeable.
I agree this is the case, but spec wise, we'll probably want to do one of the two changes:
|
Keeping the early return sounds good to me if they're indeed equivalent. |
Ok, I put the early return back in. Yes, they are equivalent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ignoring OP as there is no behavior change.
Apologies for forgetting to prefix with "Editorial: ". I got distracted. |
Fixes #9263
(See WHATWG Working Mode: Changes for more details.)
💥 Error: Wattsi server error 💥
PR Preview failed to build. (Last tried on Jun 21, 2023, 6:52 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Wattsi Server - Wattsi Server is the web service used to build the WHATWG HTML spec.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.