Permalink
Browse files

Fix summary activation algorithm

Remove bogus abort condition, as per #764 (comment) (the links there are simple tests)
  • Loading branch information...
chaals
chaals committed Mar 29, 2017
1 parent 85ab9b5 commit 51b402ad12a7168cb2dc47dbb3b63d6856c9384b
Showing with 0 additions and 2 deletions.
  1. +0 −2 sections/semantics-interactive-elements.include
@@ -199,8 +199,6 @@
<li>If this <code>summary</code> element has no parent node, then abort these steps.</li>
<li>Let parent be this <code>summary</code> element's parent node.</li>
<li>If parent is not a <code>details</code> element, then abort these steps.</li>
<li>If parent's first child <code>summary</code> element is not this <code>summary</code> element,
then abort these steps.</li>
<li>If the <code>open</code> attribute is present on parent, then remove it. Otherwise, set parent's
<code>open</code> attribute to the empty string.
<p class="note">This will then run the <a>details notification task steps</a>.</p>

1 comment on commit 51b402a

@chaals

This comment has been minimized.

Show comment
Hide comment
@chaals

chaals Mar 29, 2017

Collaborator

Whoops. Working online and committed directly instead of making a PR :(

@stevefaulkner @adanilo can you please check this?

Collaborator

chaals commented on 51b402a Mar 29, 2017

Whoops. Working online and committed directly instead of making a PR :(

@stevefaulkner @adanilo can you please check this?

Please sign in to comment.