use the afterRemoval steps to clean up implicit anchors

[keithamus]

Refs #11694 w3c/csswg-drafts#12850

Removing the implicit anchor element should always happen on hide. Chrome removes this during "remove from top layer immediately" which is not to spec (those steps do not remove implicit anchors). If an implementation was written to spec as it is now, then anchors would not properly be cleaned up.

What needs to happen is it needs to be cleaned up regardless of the fireEvents value. But also, as #11694 describes, animation timing should be taken into account. The csswg spec affords for animation timing for the overlay property, but not for other actions. w3c/csswg-drafts#12850 introduces a callback to these steps which we can then use here to clean up the implicit anchor at the right time.

• At least two implementers are interested (and none opposed):
  • …
  • …
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chromium: …
  • Gecko: …
  • WebKit: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
• Corresponding HTML AAM & ARIA in HTML issues & PRs:
• MDN issue is filed: …
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/popover.html ( diff )