Bug 184742 - AX: [macOS] WebKit hangs when triggering an alert from an AOM increment event
Summary: AX: [macOS] WebKit hangs when triggering an alert from an AOM increment event
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2018-04-18 11:23 PDT by Nan Wang
Modified: 2018-04-20 12:10 PDT (History)
12 users (show)

See Also:


Attachments
patch (10.80 KB, patch)
2018-04-18 12:06 PDT, Nan Wang
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nan Wang 2018-04-18 11:23:28 PDT
WebKit hangs when triggering an alert from an AOM increment event

<rdar://problem/39477716>
Comment 1 Nan Wang 2018-04-18 12:06:09 PDT
Created attachment 338238 [details]
patch
Comment 2 chris fleizach 2018-04-18 12:53:35 PDT
Comment on attachment 338238 [details]
patch

View in context: https://bugs.webkit.org/attachment.cgi?id=338238&action=review

> Source/WebCore/accessibility/mac/WebAccessibilityObjectWrapperMac.mm:3593
> +    else if ([action isEqualToString:@"AXSyncDecrementAction"])

Should we remove the sync versions and fix the other tests? The sync versions aren’t that real anymore. What do you think
Comment 3 Nan Wang 2018-04-18 12:58:05 PDT
(In reply to chris fleizach from comment #2)
> Comment on attachment 338238 [details]
> patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=338238&action=review
> 
> > Source/WebCore/accessibility/mac/WebAccessibilityObjectWrapperMac.mm:3593
> > +    else if ([action isEqualToString:@"AXSyncDecrementAction"])
> 
> Should we remove the sync versions and fix the other tests? The sync
> versions aren’t that real anymore. What do you think

I tried to do that but a lot of the tests are doing increment/decrement multiple times and then check the value. That would require us to put tons of setTimeout in the tests and make them less readable.

Another concern is that this is only Mac but some tests are for all platforms so it's not reasonable to make them wait.

I think the core is not changed just the timing might be affected on macOS, so maybe keeping the sync version is not a bad idea?
Comment 4 WebKit Commit Bot 2018-04-18 14:21:56 PDT
Comment on attachment 338238 [details]
patch

Clearing flags on attachment: 338238

Committed r230782: <https://trac.webkit.org/changeset/230782>
Comment 5 WebKit Commit Bot 2018-04-18 14:21:57 PDT
All reviewed patches have been landed.  Closing bug.
Comment 6 Ryan Haddad 2018-04-20 11:46:39 PDT
The test for this change is frequently failing on macOS Debug bots:
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=accessibility%2Fmac%2Fasync-increment-decrement-action.html

--- /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/accessibility/mac/async-increment-decrement-action-expected.txt
+++ /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/accessibility/mac/async-increment-decrement-action-actual.txt
@@ -6,8 +6,8 @@
 
 PASS obj.intValue is 25
 PASS obj.intValue is 25
-PASS obj.intValue is 50
-PASS obj.intValue is 50
+FAIL obj.intValue should be 50. Was 25.
+FAIL obj.intValue should be 50. Was 25.
 PASS obj.intValue is 25
 PASS successfullyParsed is true
Comment 7 Nan Wang 2018-04-20 11:47:47 PDT
(In reply to Ryan Haddad from comment #6)
> The test for this change is frequently failing on macOS Debug bots:
> https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.
> html#showAllRuns=true&tests=accessibility%2Fmac%2Fasync-increment-decrement-
> action.html
> 
> ---
> /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/
> accessibility/mac/async-increment-decrement-action-expected.txt
> +++
> /Volumes/Data/slave/highsierra-debug-tests-wk2/build/layout-test-results/
> accessibility/mac/async-increment-decrement-action-actual.txt
> @@ -6,8 +6,8 @@
>  
>  PASS obj.intValue is 25
>  PASS obj.intValue is 25
> -PASS obj.intValue is 50
> -PASS obj.intValue is 50
> +FAIL obj.intValue should be 50. Was 25.
> +FAIL obj.intValue should be 50. Was 25.
>  PASS obj.intValue is 25
>  PASS successfullyParsed is true

Ok looking
Comment 8 Nan Wang 2018-04-20 12:10:38 PDT
will be fixing the flaky test in
https://bugs.webkit.org/show_bug.cgi?id=184834