[Webkit-unassigned] [Bug 222117] New: REGRESSION (r273004): [ macOS ] media/modern-media-controls/volume-support/volume-support-drag.html is a flakey text failure

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 18 10:44:29 PST 2021


https://bugs.webkit.org/show_bug.cgi?id=222117

            Bug ID: 222117
           Summary: REGRESSION (r273004): [ macOS ]
                    media/modern-media-controls/volume-support/volume-supp
                    ort-drag.html is a flakey text failure
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: Jenner at apple.com

media/modern-media-controls/volume-support/volume-support-drag.html

is a flakey text failure in macOS. 

HISTORY URL:
https://results.webkit.org/?suite=layout-tests&test=media/modern-media-controls/volume-support/volume-support-drag.html

DIFF URL:
https://build.webkit.org/results/Apple-BigSur-Release-WK2-Tests/r273075%20(310)/media/modern-media-controls/volume-support/volume-support-drag-pretty-diff.html

DIFF TEXT:
@@ -6,19 +6,15 @@
 By default, the volume slider should be set to 0 because the media is muted
 PASS mediaController.controls.volumeSlider.value is 0
 PASS muteButton.getBoundingClientRect().width became different from 0
-PASS volumeSlider.getBoundingClientRect().width became different from 0
-
-Before starting to drag the volume slider, the media should be muted still
-PASS media.muted is true
-
-We initiated a volume slider drag, the media should no longer be muted and the volume set
-PASS media.muted became false
-PASS media.volume became 0.51
-
-We finished dragging to set the volume to 1
-PASS media.volume became 1
-PASS mediaController.controls.volumeSlider.parent.visible is true
 PASS successfullyParsed is true

 TEST COMPLETE

+
+
+
+
+0:00
+
+0:06
+


Have not reproduced yet. However, history points to flakey failures starting at r273004. There do appear to be related changes at that revision.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210218/272ddf3b/attachment.htm>


More information about the webkit-unassigned mailing list