[webkit-changes] [WebKit/WebKit] 821840: Cherry-pick 260860 at main (e9dd88dee673). https://bu...
Adrian Perez
noreply at github.com
Wed Mar 8 00:55:12 PST 2023
Branch: refs/heads/webkitglib/2.40
Home: https://github.com/WebKit/WebKit
Commit: 821840e6cf13b872dc103dce907fbbb3a9c3d19e
https://github.com/WebKit/WebKit/commit/821840e6cf13b872dc103dce907fbbb3a9c3d19e
Author: Charlie Wolfe <charliew at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
A LayoutTests/http/tests/navigation/cross-origin-iframe-location-hash-reexecute-onload-expected.txt
A LayoutTests/http/tests/navigation/cross-origin-iframe-location-hash-reexecute-onload.html
A LayoutTests/http/tests/navigation/resources/change-location-hash-onload.html
M Source/WebCore/loader/FrameLoader.cpp
Log Message:
-----------
Cherry-pick 260860 at main (e9dd88dee673). https://bugs.webkit.org/show_bug.cgi?id=252931
window.onload is repeatedly re-executed when changing URL fragment during onload
https://bugs.webkit.org/show_bug.cgi?id=252931
rdar://105158419
Reviewed by Chris Dumez.
When a cross-origin iframe changes its fragment identifier while its load event is being processed,
we end up in a state where we will continually re-fire window.onload. We should fix this by only
firing the load event on the frame's owner element. This still addresses the concern the original
change fixed (259384 at main), but without needing to always re-fire the window load event.
* LayoutTests/http/tests/navigation/cross-origin-iframe-location-hash-reexecute-onload-expected.txt: Added.
* LayoutTests/http/tests/navigation/cross-origin-iframe-location-hash-reexecute-onload.html: Added.
* LayoutTests/http/tests/navigation/resources/change-location-hash-onload.html: Added.
* Source/WebCore/loader/FrameLoader.cpp:
(WebCore::FrameLoader::loadInSameDocument):
Canonical link: https://commits.webkit.org/260860@main
Commit: d8619da8f0764aaeb902afcb017b9922c57f5fa4
https://github.com/WebKit/WebKit/commit/d8619da8f0764aaeb902afcb017b9922c57f5fa4
Author: Sihui Liu <sihui_liu at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebKit/NetworkProcess/storage/CacheStorageCache.cpp
M Source/WebKit/NetworkProcess/storage/CacheStorageDiskStore.cpp
Log Message:
-----------
Cherry-pick 260643 at main (7510aa30f017). https://bugs.webkit.org/show_bug.cgi?id=252673
Fix use-after-move in CacheStorageDiskStore::writeRecords
https://bugs.webkit.org/show_bug.cgi?id=252673
rdar://105731921
Reviewed by Youenn Fablet.
Also add WTFMove() at places that are possible to do move assignment.
* Source/WebKit/NetworkProcess/storage/CacheStorageCache.cpp:
(WebKit::CacheStorageCache::open):
(WebKit::CacheStorageCache::putRecordsInStore):
* Source/WebKit/NetworkProcess/storage/CacheStorageDiskStore.cpp:
(WebKit::decodeRecordHeader):
(WebKit::CacheStorageDiskStore::writeRecords):
Canonical link: https://commits.webkit.org/260643@main
Commit: b28d0b9ccd185301d6950b1f2dd66e09367fbeb2
https://github.com/WebKit/WebKit/commit/b28d0b9ccd185301d6950b1f2dd66e09367fbeb2
Author: Brian Weinstein <bweinstein at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M LayoutTests/http/tests/contentextensions/css-display-none.html
M LayoutTests/http/tests/contentextensions/css-display-none.html.json
M Source/WebCore/contentextensions/ContentExtensionParser.cpp
Log Message:
-----------
Cherry-pick 260638 at main (6f913a33098b). https://bugs.webkit.org/show_bug.cgi?id=252677
Content Blocker API ignores some CSS Selectors with uppercase letters.
https://bugs.webkit.org/show_bug.cgi?id=252677
rdar://105648971
Reviewed by Antti Koivisto.
The fix for https://bugs.webkit.org/show_bug.cgi?id=250609 caused us to use Quirks mode when both
parsing content blocker rules and applying them.
That caused this regression, since rules like .SomeCLass stopped working in Quirks mode.
To fix this, make us use Quirks mode when actually parsing the rules, but standard mode when
applying them, to match how the behavior was before https://bugs.webkit.org/show_bug.cgi?id=250609.
* LayoutTests/http/tests/contentextensions/css-display-none.html:
* LayoutTests/http/tests/contentextensions/css-display-none.html.json:
* Source/WebCore/contentextensions/ContentExtensionParser.cpp:
(WebCore::ContentExtensions::isValidCSSSelector):
(WebCore::ContentExtensions::contentExtensionCSSParserContext):
Canonical link: https://commits.webkit.org/260638@main
Commit: db75f8753dcd1bfad5c948c41fd249c942c374ae
https://github.com/WebKit/WebKit/commit/db75f8753dcd1bfad5c948c41fd249c942c374ae
Author: Patrick Griffis <pgriffis at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebCore/Modules/mediastream/gstreamer/GStreamerDataChannelHandler.cpp
Log Message:
-----------
Cherry-pick 260580 at main (70ed120ac0ba). https://bugs.webkit.org/show_bug.cgi?id=252601
[GStreamer] GST_WEBRTC_DATA_CHANNEL_STATE_NEW was removed in 1.21.1
https://bugs.webkit.org/show_bug.cgi?id=252601
Reviewed by Philippe Normand.
* Source/WebCore/Modules/mediastream/gstreamer/GStreamerDataChannelHandler.cpp:
(WebCore::GStreamerDataChannelHandler::checkState):
Canonical link: https://commits.webkit.org/260580@main
Commit: 136bfe7f5f5a984ea4d1086b71975164871f4d21
https://github.com/WebKit/WebKit/commit/136bfe7f5f5a984ea4d1086b71975164871f4d21
Author: Chris Dumez <cdumez at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
A LayoutTests/fast/frames/about-blank-frame-no-lazy-loading-expected.txt
A LayoutTests/fast/frames/about-blank-frame-no-lazy-loading.html
M Source/WebCore/html/HTMLFrameElementBase.cpp
M Source/WebCore/html/HTMLIFrameElement.cpp
Log Message:
-----------
Cherry-pick 260612 at main (b57dc1f8ff99). https://bugs.webkit.org/show_bug.cgi?id=252636
Regression(252852 at main) Games on kongregate.com are no longer loading
https://bugs.webkit.org/show_bug.cgi?id=252636
rdar://104392542
Reviewed by Ryosuke Niwa.
Do not lazy load iframes that have no valid URL or "about:blank" as URL. Lazily
loading such iframes has no performance benefits and can actually cause breakage
as JS (like on kongregate.com) may expect them to load synchronously.
Note that we have a more general problem where we fail to create the Frame &
initial empty document when we decide to lazy load an iframe. This is not correct,
and we should only delay the navigation to the frame URL *after* the creation of
the initial empty document. However, fixing this is a larger change and this is
not a regression from 252852 at main. As a result, I am merely adding a FIXME comment
in this patch and will address separately.
* LayoutTests/fast/frames/about-blank-frame-no-lazy-loading-expected.txt: Added.
* LayoutTests/fast/frames/about-blank-frame-no-lazy-loading.html: Added.
Add layout test coverage.
* Source/WebCore/html/HTMLFrameElementBase.cpp:
(WebCore::HTMLFrameElementBase::openURL):
* Source/WebCore/html/HTMLIFrameElement.cpp:
(WebCore::isFrameLazyLoadable):
(WebCore::HTMLIFrameElement::shouldLoadFrameLazily):
Canonical link: https://commits.webkit.org/260612@main
Commit: 093465380925c206e044df645f63a4458f4f31a6
https://github.com/WebKit/WebKit/commit/093465380925c206e044df645f63a4458f4f31a6
Author: Alex Christensen <achristensen at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebKit/Scripts/generate-serializers.py
M Source/WebKit/Scripts/webkit/tests/SerializedTypeInfo.cpp
Log Message:
-----------
Cherry-pick 260624 at main (daa46e4da058). https://bugs.webkit.org/show_bug.cgi?id=252645
Type info for members with Nullable attribute should pretend it's std::optional
https://bugs.webkit.org/show_bug.cgi?id=252645
Reviewed by Wenson Hsieh.
The generated serialization treats these members the same as std::optional,
so exposing the type info as std::optional makes the scripts that read it more correct.
* Source/WebKit/Scripts/generate-serializers.py:
(generate_serialized_type_info):
* Source/WebKit/Scripts/webkit/tests/SerializedTypeInfo.cpp:
(WebKit::allSerializedTypes):
Canonical link: https://commits.webkit.org/260624@main
Commit: 1f5cb7ee5d20dea6dd920978005ddc15767483b0
https://github.com/WebKit/WebKit/commit/1f5cb7ee5d20dea6dd920978005ddc15767483b0
Author: Tim Nguyen <ntim at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
A LayoutTests/fullscreen/event-listener-prefixed-unprefixed-expected.html
A LayoutTests/fullscreen/event-listener-prefixed-unprefixed.html
M Source/WebCore/dom/FullscreenManager.cpp
Log Message:
-----------
Cherry-pick 260651 at main (3a3294dbf52d). https://bugs.webkit.org/show_bug.cgi?id=252414
REGRESSION (257658 at main): Maximize full screen button fails to minimize once in full screen on trailers.apple.com
https://bugs.webkit.org/show_bug.cgi?id=252414
rdar://105144719
Reviewed by Chris Dumez.
The website was broken because it listens for both unprefixed & prefixed APIs to toggle between states, which ends up toggling the
wrong number of times.
To fix this, only emit unprefixed API when there is no listener for the prefixed API.
* LayoutTests/fullscreen/event-listener-prefixed-unprefixed-expected.html: Added.
* LayoutTests/fullscreen/event-listener-prefixed-unprefixed.html: Added.
* Source/WebCore/dom/FullscreenManager.cpp:
(WebCore::FullscreenManager::dispatchEventForNode):
Canonical link: https://commits.webkit.org/260651@main
Commit: 5137032cfb9b18c5734e114bbd154d784750ca54
https://github.com/WebKit/WebKit/commit/5137032cfb9b18c5734e114bbd154d784750ca54
Author: Philippe Normand <philn at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M LayoutTests/platform/glib/TestExpectations
M Source/WebCore/platform/mediastream/gstreamer/GStreamerMediaStreamSource.cpp
M Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingAudioSourceGStreamer.cpp
M Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingMediaSourceGStreamer.cpp
M Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingMediaSourceGStreamer.h
M Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingVideoSourceGStreamer.cpp
M Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingVideoSourceGStreamer.h
Log Message:
-----------
Cherry-pick 260669 at main (08a6948cfbbf). https://bugs.webkit.org/show_bug.cgi?id=252399
[GStreamer][WebRTC] Fixes for disabled audio tracks
https://bugs.webkit.org/show_bug.cgi?id=252399
Reviewed by Xabier Rodriguez-Calvar.
We should not interrupt the data flow when an outgoing media track has been disabled.
`MediaStreamTrack::enabled` is like muted, but it's a state that can be changed by the app, in
opposition with muted. So there's no need for a valve element in outgoing sources.
This patch also refactors silent/black samples pushing code in the mediastreamsrc element, some of
it was previously unsafe. And we make sure that outgoing buffers always have a valid PTS and DTS.
* LayoutTests/platform/glib/TestExpectations:
* Source/WebCore/platform/mediastream/gstreamer/GStreamerMediaStreamSource.cpp:
* Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingAudioSourceGStreamer.cpp:
(WebCore::RealtimeOutgoingAudioSourceGStreamer::setPayloadType):
* Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingMediaSourceGStreamer.cpp:
(WebCore::RealtimeOutgoingMediaSourceGStreamer::RealtimeOutgoingMediaSourceGStreamer):
(WebCore::RealtimeOutgoingMediaSourceGStreamer::~RealtimeOutgoingMediaSourceGStreamer):
(WebCore::RealtimeOutgoingMediaSourceGStreamer::start):
(WebCore::RealtimeOutgoingMediaSourceGStreamer::stop):
(WebCore::RealtimeOutgoingMediaSourceGStreamer::sourceMutedChanged):
(WebCore::RealtimeOutgoingMediaSourceGStreamer::sourceEnabledChanged):
(WebCore::RealtimeOutgoingMediaSourceGStreamer::initializeFromTrack):
* Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingMediaSourceGStreamer.h:
(WebCore::RealtimeOutgoingMediaSourceGStreamer::teardown):
* Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingVideoSourceGStreamer.cpp:
(WebCore::RealtimeOutgoingVideoSourceGStreamer::RealtimeOutgoingVideoSourceGStreamer):
(WebCore::RealtimeOutgoingVideoSourceGStreamer::teardown):
(WebCore::RealtimeOutgoingVideoSourceGStreamer::setPayloadType):
(WebCore::RealtimeOutgoingVideoSourceGStreamer::startUpdatingStats):
(WebCore::RealtimeOutgoingVideoSourceGStreamer::stopUpdatingStats):
(WebCore::RealtimeOutgoingVideoSourceGStreamer::sourceEnabledChanged):
* Source/WebCore/platform/mediastream/gstreamer/RealtimeOutgoingVideoSourceGStreamer.h:
Canonical link: https://commits.webkit.org/260669@main
Commit: 8daa4adc60dd7012ab819f91781bf400b718c13f
https://github.com/WebKit/WebKit/commit/8daa4adc60dd7012ab819f91781bf400b718c13f
Author: Sihui Liu <sihui_liu at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebKit/NetworkProcess/storage/CacheStorageCache.cpp
Log Message:
-----------
Cherry-pick 260663 at main (06e4100391f0). https://bugs.webkit.org/show_bug.cgi?id=252676
CacheStorageCache::removeRecords should remove key from m_records when its records become empty
https://bugs.webkit.org/show_bug.cgi?id=252676
rdar://105733091
Reviewed by Youenn Fablet.
They key might never be reached again, so we should not keep it in memory.
* Source/WebKit/NetworkProcess/storage/CacheStorageCache.cpp:
(WebKit::CacheStorageCache::removeRecords):
Canonical link: https://commits.webkit.org/260663@main
Commit: ea4ec9c1f0339b0d524925f966b3da662ebbd916
https://github.com/WebKit/WebKit/commit/ea4ec9c1f0339b0d524925f966b3da662ebbd916
Author: Philippe Normand <philn at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebCore/platform/graphics/gstreamer/GStreamerCommon.cpp
M Source/WebCore/platform/graphics/gstreamer/GStreamerCommon.h
M Source/WebCore/platform/gstreamer/GStreamerElementHarness.cpp
M Source/WebCore/platform/gstreamer/GStreamerElementHarness.h
M Tools/Scripts/webkitpy/port/glib.py
Log Message:
-----------
Cherry-pick 260670 at main (b646f7463534). https://bugs.webkit.org/show_bug.cgi?id=252559
[GStreamer] Harness: graph dump support
https://bugs.webkit.org/show_bug.cgi?id=252559
Reviewed by Xabier Rodriguez-Calvar.
In cases where a graph dump of the harness and its downstream harnesses is needed for debugging
purposes, it can be done by calling the `dumpGraph()` method. At runtime you need to set the
`$WEBKIT_GST_HARNESS_DUMP_DIR` environment variable to a filesystem directory path where `mmd`
[Mermaid](https://mermaid.js.org/) files will be created. Those can then be exported to SVG or
PNG using the mermaid CLI tools or the [live editor](https://mermaid.live).
* Source/WebCore/platform/graphics/gstreamer/GStreamerCommon.cpp:
(WebCore::ensureGStreamerInitialized):
(WebCore::webkitGstInitTime):
* Source/WebCore/platform/graphics/gstreamer/GStreamerCommon.h:
* Source/WebCore/platform/gstreamer/GStreamerElementHarness.cpp:
(WebCore::GStreamerElementHarness::GStreamerElementHarness):
(WebCore::MermaidBuilder::MermaidBuilder):
(WebCore::MermaidBuilder::generatePadId):
(WebCore::MermaidBuilder::getPadClass):
(WebCore::MermaidBuilder::process):
(WebCore::MermaidBuilder::dumpPad):
(WebCore::MermaidBuilder::dumpElement):
(WebCore::MermaidBuilder::describeCaps):
(WebCore::MermaidBuilder::span):
(WebCore::GStreamerElementHarness::dumpGraph):
* Source/WebCore/platform/gstreamer/GStreamerElementHarness.h:
(WebCore::GStreamerElementHarness::Stream::targetPad const):
(WebCore::GStreamerElementHarness::Stream::downstreamHarness const):
* Tools/Scripts/webkitpy/port/glib.py:
(GLibPort.setup_environ_for_server):
Canonical link: https://commits.webkit.org/260670@main
Commit: f76c91d39569535fe792eda576baf547e24935aa
https://github.com/WebKit/WebKit/commit/f76c91d39569535fe792eda576baf547e24935aa
Author: Chris Dumez <cdumez at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
A LayoutTests/http/tests/lazyload/synchronous-frame-creation-expected.txt
A LayoutTests/http/tests/lazyload/synchronous-frame-creation.html
M Source/WebCore/html/HTMLFrameElementBase.cpp
M Source/WebCore/loader/SubframeLoader.cpp
M Source/WebCore/loader/SubframeLoader.h
Log Message:
-----------
Cherry-pick 260713 at main (96e0c1e9f533). https://bugs.webkit.org/show_bug.cgi?id=252754
Lazily loaded frames should still get a contentWindow/contentDocument as soon as they get inserted into the document
https://bugs.webkit.org/show_bug.cgi?id=252754
Reviewed by Rob Buis.
Lazily loaded frames should still get a contentWindow/contentDocument as soon
as they get inserted into the document. Currently, we return null for these
until the iframe moves to the viewport and gets loaded. This behavior is
inconsistent with Chrome and recently caused breakage on
https://www.kongregate.com (Bug 252636).
* LayoutTests/http/tests/lazyload/synchronous-frame-creation-expected.txt: Added.
* LayoutTests/http/tests/lazyload/synchronous-frame-creation.html: Added.
* Source/WebCore/html/HTMLFrameElementBase.cpp:
(WebCore::HTMLFrameElementBase::openURL):
* Source/WebCore/loader/SubframeLoader.cpp:
(WebCore::FrameLoader::SubframeLoader::createFrameIfNecessary):
* Source/WebCore/loader/SubframeLoader.h:
Canonical link: https://commits.webkit.org/260713@main
Commit: 308be6926dcbf40bd493c6c3edda0fb7f7edffc1
https://github.com/WebKit/WebKit/commit/308be6926dcbf40bd493c6c3edda0fb7f7edffc1
Author: Philippe Normand <philn at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebCore/Modules/mediastream/gstreamer/GStreamerMediaEndpoint.cpp
M Source/WebCore/Modules/mediastream/gstreamer/GStreamerMediaEndpoint.h
M Source/WebCore/Modules/mediastream/gstreamer/GStreamerPeerConnectionBackend.cpp
Log Message:
-----------
Cherry-pick 260731 at main (74387c514701). https://bugs.webkit.org/show_bug.cgi?id=252756
[GStreamer][WebRTC] Renegotiation signalling improvement
https://bugs.webkit.org/show_bug.cgi?id=252756
Reviewed by Xabier Rodriguez-Calvar.
When webrtcbin emits its on-negotiation-needed it has already made sure the negotiation is really
needed according to the spec, but our implementation wasn't resetting the corresponding flag
afterwards. We now match the event serial number, similarly to the libwebrtc implementation.
* Source/WebCore/Modules/mediastream/gstreamer/GStreamerMediaEndpoint.cpp:
(WebCore::GStreamerMediaEndpoint::onNegotiationNeeded):
* Source/WebCore/Modules/mediastream/gstreamer/GStreamerMediaEndpoint.h:
(WebCore::GStreamerMediaEndpoint::isNegotiationNeeded const):
* Source/WebCore/Modules/mediastream/gstreamer/GStreamerPeerConnectionBackend.cpp:
(WebCore::GStreamerPeerConnectionBackend::isNegotiationNeeded const):
Canonical link: https://commits.webkit.org/260731@main
Commit: 5c567ba9f4fd048f51f7d57f1dc818834bb6a13b
https://github.com/WebKit/WebKit/commit/5c567ba9f4fd048f51f7d57f1dc818834bb6a13b
Author: Philippe Normand <philn at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M LayoutTests/platform/glib/TestExpectations
M Source/WebCore/platform/audio/gstreamer/AudioSourceProviderGStreamer.cpp
M Source/WebCore/platform/audio/gstreamer/AudioSourceProviderGStreamer.h
Log Message:
-----------
Cherry-pick 260742 at main (5e1b9418e1ae). https://bugs.webkit.org/show_bug.cgi?id=252751
[GStreamer][WebRTC] Disabled incoming audio track breaks webaudio provider
https://bugs.webkit.org/show_bug.cgi?id=252751
Reviewed by Xabier Rodriguez-Calvar.
Disabling an incoming audio track internally means that the mediastreamsrc switches from RTP
payloads to raw audio. The AudioSourceProvider wasn't able to reliably handle this, but switching
its internal pipeline to uridecodebin3 solves the issue. Internally uridecodebin3 will be able to
reconfigure properly.
* LayoutTests/platform/glib/TestExpectations:
* Source/WebCore/platform/audio/gstreamer/AudioSourceProviderGStreamer.cpp:
(WebCore::AudioSourceProviderGStreamer::AudioSourceProviderGStreamer):
(WebCore::AudioSourceProviderGStreamer::~AudioSourceProviderGStreamer):
(WebCore::AudioSourceProviderGStreamer::setClient):
* Source/WebCore/platform/audio/gstreamer/AudioSourceProviderGStreamer.h:
Canonical link: https://commits.webkit.org/260742@main
Commit: 117ba5cbb1d7ae2ff69f76384b228608aa5d397e
https://github.com/WebKit/WebKit/commit/117ba5cbb1d7ae2ff69f76384b228608aa5d397e
Author: Philippe Normand <philn at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebCore/platform/graphics/gstreamer/VideoTrackPrivateGStreamer.cpp
Log Message:
-----------
Cherry-pick 260732 at main (e4f3157afc6c). https://bugs.webkit.org/show_bug.cgi?id=252757
[GStreamer] Improve logging in VideoTrackPrivateGStreamer
https://bugs.webkit.org/show_bug.cgi?id=252757
Reviewed by Xabier Rodriguez-Calvar.
A webkitvideotrack gstreamer debug category can now be used to get runtime logs corresponding to
this module.
* Source/WebCore/platform/graphics/gstreamer/VideoTrackPrivateGStreamer.cpp:
(WebCore::ensureDebugCategoryInitialized):
(WebCore::VideoTrackPrivateGStreamer::VideoTrackPrivateGStreamer):
(WebCore::VideoTrackPrivateGStreamer::updateConfigurationFromTags):
(WebCore::VideoTrackPrivateGStreamer::updateConfigurationFromCaps):
Canonical link: https://commits.webkit.org/260732@main
Commit: 1eef14907582345703d00b985d6cbbe382d36e7a
https://github.com/WebKit/WebKit/commit/1eef14907582345703d00b985d6cbbe382d36e7a
Author: Chris Dumez <cdumez at apple.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebKit/UIProcess/WebProcessPool.cpp
Log Message:
-----------
Cherry-pick 260754 at main (9e54e083d6c2). https://bugs.webkit.org/show_bug.cgi?id=252843
WebProcessPool::processForNavigation() should prevent the process from getting shut down while waiting for AddAllowedFirstPartyForCookies IPC reply
https://bugs.webkit.org/show_bug.cgi?id=252843
rdar://105375981
Reviewed by Alex Christensen.
ebProcessPool::processForNavigation() should prevent the process from getting
shut down (or added to the process cache) while waiting for
AddAllowedFirstPartyForCookies IPC reply.
We recently fixed the lambda in WebPageProxy::triggerBrowsingContextGroupSwitchForNavigation()
but failed to fix this one.
* Source/WebKit/UIProcess/WebProcessPool.cpp:
(WebKit::WebProcessPool::processForNavigation):
Canonical link: https://commits.webkit.org/260754@main
Commit: 1495be3dc769dbf8dc1877970d6d9848b9220415
https://github.com/WebKit/WebKit/commit/1495be3dc769dbf8dc1877970d6d9848b9220415
Author: Žan Doberšek <zdobersek at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebCore/platform/graphics/PlatformDisplay.cpp
M Source/WebCore/platform/graphics/PlatformDisplay.h
Log Message:
-----------
Cherry-pick 261262 at main (6410ba3f6f3b). https://bugs.webkit.org/show_bug.cgi?id=253425
PlatformDisplay::eglExtensions() should initialize EGL display if necessary
https://bugs.webkit.org/show_bug.cgi?id=253425
Reviewed by Carlos Garcia Campos.
The PlatformDisplay::eglExtensions() getter should initialize EGL display if not
yet initialized, like other similar getters on PlatformDisplay do. This
initialization process will also determine extension presence and mark the
relevant extensions accordingly on the EGLExtensions struct.
* Source/WebCore/platform/graphics/PlatformDisplay.cpp:
(WebCore::PlatformDisplay::eglExtensions const):
* Source/WebCore/platform/graphics/PlatformDisplay.h:
(WebCore::PlatformDisplay::eglExtensions const): Deleted.
Canonical link: https://commits.webkit.org/261262@main
Commit: e1fd763346ae340ef44c24f1fc96e2de13351ba4
https://github.com/WebKit/WebKit/commit/e1fd763346ae340ef44c24f1fc96e2de13351ba4
Author: Diego Pino Garcia <dpino at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebKit/Platform/IPC/StreamConnectionBuffer.h
Log Message:
-----------
Cherry-pick 261255 at main (d4e7ec025851). https://bugs.webkit.org/show_bug.cgi?id=253377
[GLIB] Unreviewed, build fix for Debian Stable after 261239 at main
https://bugs.webkit.org/show_bug.cgi?id=253377
Follow-up 261239 at main.
Add missing header cstddef.
* Source/WebKit/Platform/IPC/StreamConnectionBuffer.h:
Canonical link: https://commits.webkit.org/261255@main
Commit: d93cd4c091e20ba8ef7f7f2dea590361e6c3acbf
https://github.com/WebKit/WebKit/commit/d93cd4c091e20ba8ef7f7f2dea590361e6c3acbf
Author: Adrian Perez de Castro <aperez at igalia.com>
Date: 2023-03-08 (Wed, 08 Mar 2023)
Changed paths:
M Source/WebKit/Shared/CoordinatedGraphics/threadedcompositor/ThreadedCompositor.cpp
Log Message:
-----------
Unreviewed non-unified build fix
* Source/WebKit/Shared/CoordinatedGraphics/threadedcompositor/ThreadedCompositor.cpp:
Add missing wtf/glib/RunLoopSourcePriority.h header.
Compare: https://github.com/WebKit/WebKit/compare/42a4dcf86dfc...d93cd4c091e2
More information about the webkit-changes
mailing list