commit | 180663835647ab9427efdedb40275704afb98cc8 | [log] [tgz] |
---|---|---|
author | mrajca@apple.com <mrajca@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Fri Jan 04 19:45:09 2019 +0000 |
committer | mrajca@apple.com <mrajca@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Fri Jan 04 19:45:09 2019 +0000 |
tree | 62616207b0285d57052f550ae3402c238bc36375 | |
parent | 619a8b9fa8c1f2487981e786178d656b8244f87b [diff] |
Make DidPlayMediaPreventedFromPlaying autoplay event more generic. https://bugs.webkit.org/show_bug.cgi?id=193128 rdar://34554231 Reviewed by Jer Noble. Today, the "DidPlayMediaPreventedFromPlaying" autoplay event is only sent for media prevented from autoplaying. It could be generalized to a "DidPlayMediaWithUserGesture" event along with a flag that indicates whether or not autoplay was actually prevented. Source/WebCore: Moreover, we can include a flag that indicates whether the media element in question is main content. Clients will then know in more cases when media was played with a user gesture, whether or not it has audio, as well as its main content status. While the main content heuristics may not be perfect, they covered the top 20 video-centric websites that this was tested with and are meant to be used by clients for data evaluation purposes. As part of this, the PlaybackWithoutUserGesture enum was renamed to AutoplayEventPlaybackState since it now also applies to cases where there is a user gesture. The `m_playbackWithoutUserGestureStartedTime` member variable was also removed in favor of `playbackStartedTime` which also covers all the cases we care about. Tests: existing API tests were updated to reflect the new names. New API tests were added for the new case in which the "DidPlayMediaWithUserGesture" event is sent. * html/HTMLMediaElement.cpp: (WebCore::convertEnumerationToString): Update to new enum cases. (WebCore::HTMLMediaElement::setReadyState): Ditto. (WebCore::HTMLMediaElement::play): Ditto. (WebCore::HTMLMediaElement::playInternal): Also cover the case where playback was not prevented but there was a user gesture. (WebCore::HTMLMediaElement::pauseInternal): Use new name. (WebCore::HTMLMediaElement::setVolume): Use new name. (WebCore::HTMLMediaElement::playbackProgressTimerFired): Dispatch the DidPlayMediaWithUserGesture event when playback was started with a user gesture as well. (WebCore::HTMLMediaElement::mediaPlayerDidAddAudioTrack): Use new name. (WebCore::HTMLMediaElement::mediaPlayerTimeChanged): Ditto. (WebCore::HTMLMediaElement::mediaPlayerCharacteristicChanged): Ditto. (WebCore::HTMLMediaElement::stopWithoutDestroyingMediaPlayer): Ditto. (WebCore::HTMLMediaElement::handleAutoplayEvent): Pass along new media state. (WebCore::HTMLMediaElement::userDidInterfereWithAutoplay): Use new name. (WebCore::HTMLMediaElement::setAutoplayEventPlaybackState): Stop setting m_playbackWithoutUserGestureStartedTime in favor of using playbackStartedTime. (WebCore::HTMLMediaElement::updateShouldPlay): Use new name. (WebCore::HTMLMediaElement::setPlaybackWithoutUserGesture): Renamed. * html/HTMLMediaElement.h: (WTF::LogArgument<WebCore::HTMLMediaElement::AutoplayEventPlaybackState>::toString): Renamed from... (WTF::LogArgument<WebCore::HTMLMediaElement::PlaybackWithoutUserGesture>::toString): * html/MediaElementSession.cpp: (WebCore::MediaElementSession::isMainContentForPurposesOfAutoplayEvents const): Don't do the hit testing check for the purposes of autoplay events. It seems to fail on the basic Vimeo player due to overlapping divs. (WebCore::isElementMainContentForPurposesOfAutoplay): (WebCore::MediaElementSession::updateIsMainContent const): Keep the existing behavior here of hit testing. (WebCore::isMainContentForPurposesOfAutoplay): Renamed. * html/MediaElementSession.h: * page/AutoplayEvent.h: Source/WebKit: Tests: existing API tests were updated to reflect the new names. New API tests were added for the new case in which the "DidPlayMediaWithUserGesture" event is sent. * Shared/WebCoreArgumentCoders.h: Take into account new flags. * UIProcess/API/C/WKPage.cpp: Ditto. (WKPageSetPageUIClient): * UIProcess/API/C/WKPageUIClient.h: Ditto. * UIProcess/API/Cocoa/WKUIDelegatePrivate.h: Ditto. * UIProcess/Cocoa/UIDelegate.mm: Ditto. (WebKit::toWKAutoplayEventFlags): (WebKit::toWKAutoplayEvent): Tools: Tests: existing API tests were updated to reflect the new names. New API tests were added for the new case in which the "DidPlayMediaWithUserGesture" event is sent. * TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj: * TestWebKitAPI/Tests/WebKit/long-test.mp4: Added. * TestWebKitAPI/Tests/WebKitCocoa/WebsitePolicies.mm: (TEST): * TestWebKitAPI/Tests/WebKitCocoa/audio-with-play-button.html: Added. * TestWebKitAPI/Tests/WebKitCocoa/video-with-play-button.html: Added. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@239625 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
or
git clone https://git.webkit.org/git/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
If you don‘t want to use Git, run the following command to check out WebKit’s Subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within Xcode.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator.
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.