commit | ffc46620d9231fe96f6aef8fef2cd94aa3d93a83 | [log] [tgz] |
---|---|---|
author | wenson_hsieh@apple.com <wenson_hsieh@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Mon Oct 21 20:19:53 2019 +0000 |
committer | wenson_hsieh@apple.com <wenson_hsieh@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Mon Oct 21 20:19:53 2019 +0000 |
tree | 10cb1507b00726822bca80bfcc72d96bc8c8ecb6 | |
parent | c27e52ec2eefea39423e8eef58df2aebc1b5417d [diff] |
[Clipboard API] Implement ClipboardItem.getType() for platform clipboard items https://bugs.webkit.org/show_bug.cgi?id=203168 Reviewed by Tim Horton. Source/WebCore: This patch completes support for ClipboardItem.getType(). Tests: editing/async-clipboard/clipboard-change-data-while-getting-type.html editing/async-clipboard/clipboard-get-type-with-old-items.html editing/async-clipboard/clipboard-item-get-type-basic.html ClipboardTests.ReadMultipleItems * Modules/async-clipboard/Clipboard.cpp: (WebCore::Clipboard::getType): Implement getType(). If the given clipboard item is being tracked as one of the active clipboard items, then allow it to read data from the platform pasteboard. We use existing pasteboard reading methods and classes (PasteboardPlainText and WebContentMarkupReader) to ask the platform pasteboard for text and markup data, respectively, and go through readURL() for "text/uri-list". Before exposing any data to the page, we additionally check that the change count of the pasteboard is still what we started with when setting up the current session. If this is not the case, we reject the promise and immediately clear out the session. (WebCore::Clipboard::activePasteboard): * Modules/async-clipboard/Clipboard.h: * dom/DataTransfer.h: Drive-by tweak: make the WebContentReadingPolicy enum class narrower. * platform/Pasteboard.h: Add an enum flag for allowing or ignoring the platform URL type when reading plain text from the platform pasteboard. We use this in Clipboard::getType() to ignore URLs on the platform pasteboard when plain text, since the plain text reader would otherwise prefer URLs over plain text by default, and read the URL type instead of the plain text type. * platform/StaticPasteboard.h: * platform/gtk/PasteboardGtk.cpp: (WebCore::Pasteboard::read): * platform/ios/PasteboardIOS.mm: (WebCore::Pasteboard::read): * platform/libwpe/PasteboardLibWPE.cpp: (WebCore::Pasteboard::read): * platform/mac/PasteboardMac.mm: (WebCore::Pasteboard::read): * platform/win/PasteboardWin.cpp: (WebCore::Pasteboard::read): Tools: Add support for the new layout tests, as well as a new API test. * DumpRenderTree/ios/UIScriptControllerIOS.h: * DumpRenderTree/ios/UIScriptControllerIOS.mm: (WTR::UIScriptControllerIOS::copyText): Implement UIScriptController.copyText in WebKit1. This is used in one of the new layout tests, which passes in WebKit1 on macOS and iOS. * DumpRenderTree/mac/DumpRenderTreePasteboard.mm: (-[LocalPasteboard declareTypes:owner:]): (-[LocalPasteboard addTypes:owner:]): (-[LocalPasteboard _addTypesWithoutUpdatingChangeCount:owner:]): Adjust logic when declaring types on the platform pasteboard, such that it behaves more like the platform; when declaring types, even if the owner doesn't change, the change count should still get bumped up by 1. * DumpRenderTree/mac/UIScriptControllerMac.h: * DumpRenderTree/mac/UIScriptControllerMac.mm: (WTR::UIScriptControllerMac::copyText): * TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj: * TestWebKitAPI/Tests/WebKitCocoa/ClipboardTests.mm: Added. (-[TestWKWebView readClipboard]): (createWebViewForClipboardTests): (writeMultipleObjectsToPlatformPasteboard): Add a new API test to verify that clipboard items contain the right data when writing multiple items (each with different sets of types) to the platform pasteboard using native APIs. * TestWebKitAPI/Tests/WebKitCocoa/clipboard.html: Added. * WebKitTestRunner/mac/WebKitTestRunnerPasteboard.mm: (-[LocalPasteboard declareTypes:owner:]): (-[LocalPasteboard addTypes:owner:]): (-[LocalPasteboard _addTypesWithoutUpdatingChangeCount:owner:]): LayoutTests: Add 3 new layout tests. * editing/async-clipboard/clipboard-change-data-while-getting-type-expected.txt: Added. * editing/async-clipboard/clipboard-change-data-while-getting-type.html: Added. Add a layout test to verify that if the pasteboard changes right after the page has obtained clipboard items, the page should not be able to fetch the new contents of the pasteboard using these clipboard items. * editing/async-clipboard/clipboard-get-type-with-old-items.html: Added. * editing/async-clipboard/clipboard-get-type-with-old-items-expected.txt: Added. Add a layout test to verify that after attempting to get data from invalid (stale) items, the page is still capable of reading data from valid clipboard items. * editing/async-clipboard/clipboard-item-get-type-basic-expected.txt: Added. * editing/async-clipboard/clipboard-item-get-type-basic.html: Added. Add a layout test to verify that after writing multiple types to the clipboard using the DataTransfer API, we should be able to read them back using the async clipboard API, as a single ClipboardItem, and also get data out of the clipboard item using ClipboardItem.getType. * editing/async-clipboard/resources/async-clipboard-helpers.js: * platform/win/TestExpectations: * resources/ui-helper.js: (window.UIHelper.async.copyText): (window.UIHelper): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@251377 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.