Branch: refs/heads/webkitglib/2.46
Home: https://github.com/WebKit/WebKit
Commit: 9dfc421b3a0d04e469efd61f133d3d339abfec35
https://github.com/WebKit/WebKit/commit/9dfc421b3a0d04e469efd61f133d3d339abfec35
Author: Said Abou-Hallawa <s...@apple.com>
Date: 2024-09-24 (Tue, 24 Sep 2024)
Changed paths:
A LayoutTests/fast/images/async-image-large-animated-disabled-expected.txt
A LayoutTests/fast/images/async-image-large-animated-disabled.html
A LayoutTests/fast/images/resources/animated-red-green-blue-400x400.gif
M Source/WebCore/platform/graphics/BitmapImageSource.cpp
M Source/WebCore/rendering/RenderBoxModelObject.cpp
Log Message:
-----------
Cherry-pick 283753@main (a3254962b06e).
https://bugs.webkit.org/show_bug.cgi?id=278593
REGRESSION(/276827@main): Large animated images are always decoded
asynchronously
https://bugs.webkit.org/show_bug.cgi?id=278593
rdar://134597661
Reviewed by Simon Fraser.
The large animated images should be decoded asynchronously if the setting
AnimatedImageAsyncDecodingEnabled is true. The only exception is the first
frame
has to be decoded synchronously only for the first time.
* LayoutTests/fast/images/async-image-large-animated-disabled-expected.txt:
Added.
* LayoutTests/fast/images/async-image-large-animated-disabled.html: Added.
* LayoutTests/fast/images/resources/animated-red-green-blue-400x400.gif:
Added.
* Source/WebCore/platform/graphics/BitmapImageSource.cpp:
(WebCore::BitmapImageSource::startAnimation):
(WebCore::BitmapImageSource::imageFrameDecodeAtIndexHasFinished):
(WebCore::BitmapImageSource::cacheNativeImageAtIndex):
(WebCore::BitmapImageSource::currentNativeImageForDrawing):
* Source/WebCore/rendering/RenderBoxModelObject.cpp:
(WebCore::RenderBoxModelObject::decodingModeForImageDraw const):
Canonical link: https://commits.webkit.org/283753@main
Canonical link: https://commits.webkit.org/282416.134@webkitglib/2.46
Commit: 2d193f1083166310a49d0a94abffa38be0e6bf10
https://github.com/WebKit/WebKit/commit/2d193f1083166310a49d0a94abffa38be0e6bf10
Author: Michael Catanzaro <mcatanz...@redhat.com>
Date: 2024-09-24 (Tue, 24 Sep 2024)
Changed paths:
M Source/WebKit/UIProcess/Launcher/ProcessLauncher.cpp
M Source/WebKit/UIProcess/Launcher/ProcessLauncher.h
M Source/WebKit/UIProcess/Launcher/glib/ProcessLauncherGLib.cpp
Log Message:
-----------
Cherry-pick 284159@main (7dd6aeafdd8e).
https://bugs.webkit.org/show_bug.cgi?id=280073
REGRESSION(283414@main): [WPE][GTK] File descriptor leak if process launch
is canceled immediately
https://bugs.webkit.org/show_bug.cgi?id=280073
Reviewed by Carlos Garcia Campos.
If the socket monitor callback is not called, the server socket is
leaked. Oops.
I am separately working on converting ProcessLauncher and
IPC::Connection to use UnixFileDescriptor, which will make errors like
this less likely. But that's a large change, and we should fix this
with a small change.
* Source/WebKit/UIProcess/Launcher/ProcessLauncher.cpp:
* Source/WebKit/UIProcess/Launcher/ProcessLauncher.h:
* Source/WebKit/UIProcess/Launcher/glib/ProcessLauncherGLib.cpp:
(WebKit::ProcessLauncher::platformDestroy):
(WebKit::ProcessLauncher::launchProcess):
Canonical link: https://commits.webkit.org/284159@main
Canonical link: https://commits.webkit.org/282416.135@webkitglib/2.46
Compare: https://github.com/WebKit/WebKit/compare/b5b2394216d9...2d193f108316
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes
