Google Git
Sign in
chromium / external / github.com / WebKit / webkit / refs/heads/webkitglib/2.44
commit1e1bf92025ba3df8a0762fbadaa8a3bec1b83504[log] [tgz]
authorPrzemyslaw Gorszkowski <pgorszkowski@igalia.com>Mon Oct 07 12:21:15 2024
committerAdrian Perez de Castro <aperez@igalia.com>Mon Oct 07 12:44:32 2024
tree9ca0d32dc4e82a3f3357514f732198db53f6f5a5
parentc2959a39659a00d8333595cafa57c0b236d19373 [diff]
Cherry-pick 284757@main (7f5e13b54893). https://bugs.webkit.org/show_bug.cgi?id=280612

    [WPE][GTK] visible rect in case animations is not correctly calculated
    https://bugs.webkit.org/show_bug.cgi?id=280612

    Reviewed by Miguel Gomez.

    For animations starting partially outside the viewport were not fully rendered when
    the first frame entered the visible area. This caused incomplete or cut-off frames
    during the initial stages of the animation. The issue was more noticeable on low-end
    devices(RPi) or during slow-motion or frame-by-frame analysis of the recordings on x86.

    With this change the visible rect is extended with the elements which are currently
    not fully visible but they will be in a future bacause of animations.

    Y* Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedGraphicsLayer.cpp:
    (WebCore::CoordinatedGraphicsLayer::transformedVisibleRectIncludingFuture):
    (WebCore::CoordinatedGraphicsLayer::updateContentBuffers):
    (WebCore::CoordinatedGraphicsLayer::computeTransformedVisibleRect):
    * Source/WebCore/platform/graphics/texmap/coordinated/CoordinatedGraphicsLayer.h:

    Canonical link: https://commits.webkit.org/284757@main

Canonical link: https://commits.webkit.org/274313.448@webkitglib/2.44
2 files changed
tree: 9ca0d32dc4e82a3f3357514f732198db53f6f5a5
  1. .github/
  2. Configurations/
  3. JSTests/
  4. LayoutTests/
  5. ManualTests/
  6. metadata/
  7. PerformanceTests/
  8. resources/
  9. Source/
  10. Tools/
  11. WebDriverTests/
  12. WebKit.xcworkspace/
  13. WebKitLibraries/
  14. Websites/
  15. .ccls
  16. .clang-format
  17. .clangd
  18. .dir-locals.el
  19. .editorconfig
  20. .gitattributes
  21. .gitignore
  22. .submitproject
  23. CMakeLists.txt
  24. CMakePresets.json
  25. Introduction.md
  26. Makefile
  27. Makefile.shared
  28. ReadMe.md
ReadMe.md

WebKit

WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications. For more information about WebKit, see the WebKit project website.

Trying the Latest

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.

Reporting Bugs

  1. Search WebKit Bugzilla to see if there is an existing report for the bug you've encountered.
  2. Create a Bugzilla account to report bugs (and comment on them) if you haven't done so already.
  3. File a bug in accordance with our guidelines.

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.

Getting the Code

Run the following command to clone WebKit's Git repository:

git clone https://github.com/WebKit/WebKit.git WebKit

Building WebKit

Building macOS Port

Install Xcode and its command line tools if you haven't done so already:

  1. Install Xcode Get Xcode from https://developer.apple.com/downloads. To build WebKit for OS X, Xcode 5.1.1 or later is required. To build WebKit for iOS Simulator, Xcode 7 or later is required.
  2. Install the Xcode Command Line Tools In Terminal, run the command: 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.

Using Xcode

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.

Embedded Builds

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.

Building the GTK Port

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.

Building the WPE Port

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

Building Windows Port

For building WebKit on Windows, see the WebKit on Windows page.

Running WebKit

With Safari and Other macOS Applications

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>

iOS Simulator

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.

Linux Ports

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.

Contribute

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.