<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - accessibility/mac/aria-expanded-notifications.html is flaky"
href="https://bugs.webkit.org/show_bug.cgi?id=149510#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - accessibility/mac/aria-expanded-notifications.html is flaky"
href="https://bugs.webkit.org/show_bug.cgi?id=149510">bug 149510</a>
from <span class="vcard"><a class="email" href="mailto:mmaxfield@apple.com" title="Myles C. Maxfield <mmaxfield@apple.com>"> <span class="fn">Myles C. Maxfield</span></a>
</span></b>
<pre>The problem is triggered by our resumable parser.
if (elapsedTime > m_parserTimeLimit)
session.needsYield = true;
AXLoadComplete gets called synchronously from DocumentLoader::finishedLoading(). This means that the order of the AXLoadComplete message isn't FIFO:
If the parser yielded previously, the AXLoadComplete will be handled after some AX messages had been handled. If the parser hadn't yielded, the AXLoadComplete will be the first message processed (no matter what had been queued up before it).
I assume that making AXLoadComplete asynchronous is not possible. Therefore, it seems the test should be relaxed to handle the case of various orderings.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>