commit | 74581db8cf8dcdc57ec33dc38e9f914ad9d881e3 | [log] [tgz] |
---|---|---|
author | timothy_horton@apple.com <timothy_horton@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sat May 06 01:39:00 2017 +0000 |
committer | timothy_horton@apple.com <timothy_horton@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sat May 06 01:39:00 2017 +0000 |
tree | 4031e119e411d499e4af799b55afd50ee7545c58 | |
parent | abe59cfd35c658a025334dabd3411e14e2b25499 [diff] |
[Mac] Adjust cursor position for dragged link (and stop it from moving based on how fast you are dragging) https://bugs.webkit.org/show_bug.cgi?id=171764 <rdar://problem/32005865> Reviewed by Simon Fraser. * page/DragController.cpp: (WebCore::DragController::startDrag): Compute dragImageAnchorPoint only if it is needed. Don't compute a random unused imageRect. Factor link drag image offset computation out into DragImage functions for platforms to override. Pass dragOrigin (the mouseDown point), not mouseDraggedPoint, to doSystemDrag, just like all the other drag types. This plus the WebKit2 change makes the link stable vs. the cursor, instead of positioned based on how fast you move after the mouse down. * page/DragController.h: * page/gtk/DragControllerGtk.cpp: * page/mac/DragControllerMac.mm: * page/win/DragControllerWin.cpp: Move LinkDragBorderInset into DragImage, and share between the non-Mac platforms. * platform/DragImage.cpp: (WebCore::dragOffsetForLinkDragImage): (WebCore::anchorPointForLinkDragImage): * platform/DragImage.h: As previously mentioned, move the computation of drag image offset here. * platform/mac/DragImageMac.mm: (WebCore::dragOffsetForLinkDragImage): (WebCore::anchorPointForLinkDragImage): Put the new drag image to the bottom right of the cursor. * UIProcess/Cocoa/WebViewImpl.mm: (WebKit::WebViewImpl::dragImageForView): Always use the last mouse down event to originate the drag; this was a 2004 hack to work around a seemingly-fixed macOS bug that somehow propagated into WebKit2. With WebKit2, this would cause trouble because currentEvent could move on during the bounce to the Web Content process and back, causing the delta between clientPoint and the mouse point to be dependent on timing, and thus causing the link to sit at timing-dependent distance from the cursor, instead of exactly where dragOffsetForLinkDragImage placed it. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@216303 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.
Downloading Safari Technology Preview to test the latest version of WebKit.
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
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.
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 WebKit.
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.
Install the dependencies by running the following command:
Tools/gtk/install-dependencies
Then run the following command to build additional dependencies:
Tools/Scripts/update-webkitgtk-libs
Run the following command to build WebKit with debugging symbols for GTK+ port:
Tools/Scripts/build-webkit --debug --gtk
Note that the procedure for building a release tarball is different. For more information, see the wiki page.
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
.
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.