Skip to content

Commit

Permalink
Handle attribute changes after changing attribute
Browse files Browse the repository at this point in the history
At least in chromium, synchronous internal listeners for attribute
changes which are run as "attribute change steps" are run after the
attribute is actually changed, not before.

This affects popover attribute related algorithms in HTML:
whatwg/html#9048 (comment)
  • Loading branch information
josepharhar committed Mar 25, 2023
1 parent 90691ba commit 4880751
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions dom.bs
Original file line number Diff line number Diff line change
Expand Up @@ -6185,10 +6185,10 @@ given a <var>document</var>, <var>localName</var>, <var>namespace</var>, and opt
<a>attribute</a> <var>attribute</var> to <var>value</var>, run these steps:

<ol>
<li><p>Set <var>attribute</var>'s <a for=Attr>value</a> to <var>value</var>.

<li><p><a>Handle attribute changes</a> for <var>attribute</var> with <var>attribute</var>'s
<a for=Attr>element</a>, <var>attribute</var>'s <a for=Attr>value</a>, and <var>value</var>.

<li><p>Set <var>attribute</var>'s <a for=Attr>value</a> to <var>value</var>.
</ol>

<p>To <dfn export id=concept-element-attributes-append lt="append an attribute">append</dfn> an
Expand Down

0 comments on commit 4880751

Please sign in to comment.