commit | 73fef1e0cc8cc4d7c57feb629c8c86281a66cfca | [log] [tgz] |
---|---|---|
author | graouts@webkit.org <graouts@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Jan 26 17:41:07 2022 +0000 |
committer | graouts@webkit.org <graouts@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Jan 26 17:41:07 2022 +0000 |
tree | 79520c797a69a4fb39e61db8f6877ebd4c3a3b49 | |
parent | 5526c0b1aad6c8325cc20301f46bb77dd7f909cf [diff] |
[Web Inspector] Graphics tab should display pseudo-elements for more than ::before and ::after https://bugs.webkit.org/show_bug.cgi?id=235234 <rdar://87766777> Reviewed by Devin Rousso. Source/JavaScriptCore: Add a new `DOM.Styleable` type to be used as the parameter type for `requestEffectTarget()` callbacks. * inspector/protocol/Animation.json: * inspector/protocol/DOM.json: Source/WebCore: Until now, we would pass the result of KeyframeEffect::targetElementOrPseudoElement() to InspectorAnimationAgent::willApplyKeyframeEffect(). This meant that the inspector would only be told of an animation target as an Element or a PseudoElement but not as an Element / PseudoId pair, thus only allowing ::before and ::after to be represented since only those pseudo-elements create a PseudoElement. We now pass a Styleable, which encapsulate an Element / PseudoId pair, to InspectorAnimationAgent::willApplyKeyframeEffect(). Additionally, the Styleable target is read from the effect for callbacks provided to requestEffectTarget(). Sadly, we still rely on PseudoElement, but this patch at least removes all use of PseudoElement from KeyframeEffect and pushes it down to InspectorDOMAgent with a new static method elementToPushForStyleable() which the new pushStyleableElementToFrontend() and pushStyleablePathToFrontend() methods use to turn the Styleable to an Element or PseudoElement. In the future, we would need to further remove PseudoElement from Web Inspector and expose something similar to Styleable throughout the codebase, or find some other way to encapsulate an Element / PseudoId pair. * animation/KeyframeEffect.cpp: (WebCore::KeyframeEffect::apply): (WebCore::KeyframeEffect::targetElementOrPseudoElement const): Deleted. * animation/KeyframeEffect.h: (WebCore::KeyframeEffect::target const): * inspector/InspectorInstrumentation.cpp: (WebCore::InspectorInstrumentation::willApplyKeyframeEffectImpl): * inspector/InspectorInstrumentation.h: (WebCore::InspectorInstrumentation::willApplyKeyframeEffect): * inspector/agents/InspectorAnimationAgent.cpp: (WebCore::InspectorAnimationAgent::requestEffectTarget): (WebCore::InspectorAnimationAgent::willApplyKeyframeEffect): * inspector/agents/InspectorAnimationAgent.h: * inspector/agents/InspectorCSSAgent.cpp: (WebCore::InspectorCSSAgent::protocolValueForPseudoId): (WebCore::protocolValueForPseudoId): Deleted. * inspector/agents/InspectorCSSAgent.h: * inspector/agents/InspectorDOMAgent.cpp: (WebCore::elementToPushForStyleable): (WebCore::InspectorDOMAgent::pushStyleableElementToFrontend): (WebCore::InspectorDOMAgent::pushStyleablePathToFrontend): * inspector/agents/InspectorDOMAgent.h: Source/WebInspectorUI: Add a new `DOMStyleable` model class to match the new `DOM.Styleable` protocol type. When calling Animation.requestEffectTarget(), we now use this new DOMStyleable class to display pseudo-elements other than ::before or ::after in the Graphics tab. * UserInterface/Base/DOMUtilities.js: (WI.linkifyStyleable): * UserInterface/Main.html: * UserInterface/Models/Animation.js: (WI.Animation.prototype.requestEffectTarget): * UserInterface/Models/DOMStyleable.js: Added. (WI.DOMStyleable.prototype.fromPayload): (WI.DOMStyleable.prototype.get node): (WI.DOMStyleable.prototype.get pseudoId): (WI.DOMStyleable.prototype.get displayName): (WI.DOMStyleable): * UserInterface/Test.html: * UserInterface/Views/AnimationCollectionContentView.js: (WI.AnimationCollectionContentView.prototype._handleContentViewMouseEnter): * UserInterface/Views/AnimationContentView.js: (WI.AnimationContentView.prototype._refreshSubtitle): * UserInterface/Views/AnimationDetailsSidebarPanel.js: (WI.AnimationDetailsSidebarPanel.prototype._refreshIdentitySection): LayoutTests: Check that requestEffectTarget() returns the correct Styleable by checking whether it's defined or null, and checking its `node` and `pseudoId` members. * inspector/animation/targetChanged-expected.txt: * inspector/animation/targetChanged.html: git-svn-id: http://svn.webkit.org/repository/webkit/trunk@288623 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.