commit | 0e57035dc9159e37bc5a8ab7b9e7a81f7fd5a7f2 | [log] [tgz] |
---|---|---|
author | graouts@webkit.org <graouts@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sun Jan 23 21:50:29 2022 +0000 |
committer | graouts@webkit.org <graouts@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sun Jan 23 21:50:29 2022 +0000 |
tree | 013c07854ed49b6e80d5375ccd613b2a44b78e92 | |
parent | 984f150f8c5e782c4f638a98af0f73b51f501835 [diff] |
[Model] Add load and error events to distinguish resource load from model readiness https://bugs.webkit.org/show_bug.cgi?id=233706 rdar://85922697 Reviewed by Chris Dumez and Dean Jackson. Source/WebCore: Test: model-element/model-element-error-and-load-events.html Prior to this patch, <model> elements had a "ready" promise which resolved once the resource had been loaded. However, this promise should be used when the <model> is fully ready, and this is done on macOS and iOS asynchronously after the resource has been loaded by the supporting ARQL framework. So we need a way to monitor success or failure of the resource load specifically. To that end, and matching the <img> element, we dispatch "load" and "error" events on <model> elements and add a "complete" property to indicate whether the resource is loaded. Meanwhile, the "ready" promise is now resolved when the model is fully loaded by the supporting framework, indicating that further APIs are safe to use. Since creating the support ARQL object for macOS and iOS also requires the <model> element's renderer being available, we opt into "custom style resolve callbacks" so that we may implement didAttachRenderers() on HTMLModelElement and keep track of renderer availability before attempting to create the ModelPlayer. * Modules/model-element/HTMLModelElement.cpp: (WebCore::HTMLModelElement::HTMLModelElement): (WebCore::HTMLModelElement::create): (WebCore::HTMLModelElement::setSourceURL): (WebCore::HTMLModelElement::didAttachRenderers): (WebCore::HTMLModelElement::notifyFinished): (WebCore::HTMLModelElement::modelDidChange): (WebCore::HTMLModelElement::createModelPlayer): (WebCore::HTMLModelElement::didFinishLoading): (WebCore::HTMLModelElement::didFailLoading): (WebCore::HTMLModelElement::activeDOMObjectName const): (WebCore::HTMLModelElement::virtualHasPendingActivity const): * Modules/model-element/HTMLModelElement.h: * Modules/model-element/HTMLModelElement.idl: Tools: Use the "load" event instead of the "ready" promise for this test which only requires monitoring the <model> resource being loaded. * TestWebKitAPI/Tests/ios/DragAndDropTestsIOS.mm: (TestWebKitAPI::TEST): LayoutTests: Remove existing tests around resource loading and recreate them in terms of "load" and "error" events in model-element/model-element-error-and-load-events.html and in terms of the ready promise in model-element/model-element-ready.html. Other tests using model.ready for other purposes are also rewritten using events. * model-element/model-element-contents-layer-updates-with-clipping.html: * model-element/model-element-contents-layer-updates.html: * model-element/model-element-error-and-load-events-expected.txt: Added. * model-element/model-element-error-and-load-events.html: Added. * model-element/model-element-graphics-layers-opacity.html: * model-element/model-element-graphics-layers.html: * model-element/model-element-ready-expected.txt: * model-element/model-element-ready-load-aborted-expected.txt: Removed. * model-element/model-element-ready-load-aborted.html: Removed. * model-element/model-element-ready-load-failed-expected.txt: Removed. * model-element/model-element-ready-load-failed.html: Removed. * model-element/model-element-ready.html: * model-element/resources/model-element-test-utils.js: Added. (const.createModelAndSource): * platform/ios-simulator/TestExpectations: * platform/mac/TestExpectations: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@288424 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@github.com:WebKit/WebKit.git WebKit
or
git clone https://github.com/WebKit/WebKit.git WebKit
If you want to be able to track Subversion revision from your git checkout, you can run the following command to do so:
Tools/Scripts/git-webkit setup-git-svn
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.
iOS, tvOS and watchOS are all considered embedded builds. The first time after you install a new Xcode, you will need to run:
sudo Tools/Scripts/configure-xcode-for-embedded-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 embedded simulators:
Tools/Scripts/build-webkit --debug --<platform>-simulator
or embedded devices:
Tools/Scripts/build-webkit --debug --<platform>-device
where platform
is ios
, tvos
or watchos
.
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.