text-wrap balance should consider line-clamp when balancing #23479

vitorroriz · 2024-01-30T00:59:26Z

`c1353df`

text-wrap balance should consider line-clamp when balancing
https://bugs.webkit.org/show_bug.cgi?id=268302
rdar://121858978

Reviewed by Alan Baradlay.

According to spec resolution [1], if line-clamp
is defined, text-wrap: balance should balance
only within the clamped lines.

Up to this patch, we would balance taking into
consideration all the lines and we would clamp
it after balance.

This patches makes InlineContentBalancer::initialize()
take the maximum number of visible lines into account,
based into the line-clamp property.

Also, this allows for a small optimization:
If line-clamp clamps to 1 line, we can skip balacing.

[1] w3c/csswg-drafts#9310

* LayoutTests/TestExpectations:
* Source/WebCore/layout/formattingContexts/block/BlockLayoutState.h:
(WebCore::Layout::BlockLayoutState::LineClamp::allowedLineCount const):
* Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.cpp:
(WebCore::Layout::InlineContentBalancer::initialize):
(WebCore::Layout::InlineContentBalancer::computeBalanceConstraints):
* Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.h:
* Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp:
(WebCore::Layout::InlineFormattingContext::createDisplayContentForInlineContent):

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

867f21f

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	~~🛠 wincairo~~
✅ 🧪 bindings	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	~~🧪 wpe-wk2~~
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	~~🧪 api-mac~~	~~🧪 api-wpe~~
	~~🧪 ios-wk2-wpt~~	~~🧪 mac-wk1~~	✅ 🛠 gtk
	✅ 🧪 api-ios	~~🧪 mac-wk2~~	~~🧪 gtk-wk2~~
	~~🛠 tv~~	~~🧪 mac-AS-debug-wk2~~	~~🧪 api-gtk~~
	~~🛠 tv-sim~~
✅ 🛠 🧪 merge	~~🛠 watch~~
	✅ 🛠 watch-sim

webkit-early-warning-system · 2024-01-30T01:03:13Z

EWS run on previous version of this PR (hash b4d42f2)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
~~🧪 style~~	~~🛠 ios~~	~~🛠 mac~~	⏳ 🛠 wpe	⏳ 🛠 wincairo
~~🧪 bindings~~	~~🛠 ios-sim~~	~~🛠 mac-AS-debug~~	⏳ 🧪 wpe-wk2
~~🧪 webkitperl~~	~~🧪 ios-wk2~~	~~🧪 api-mac~~	⏳ 🧪 api-wpe
⏳ 🧪 webkitpy	~~🧪 ios-wk2-wpt~~	~~🧪 mac-wk1~~	⏳ 🛠 gtk
⏳ 🛠 🧪 jsc	~~🧪 api-ios~~	~~🧪 mac-wk2~~	⏳ 🧪 gtk-wk2
⏳ 🛠 🧪 jsc-arm64	⏳ 🛠 tv	~~🧪 mac-AS-debug-wk2~~	⏳ 🧪 api-gtk
	⏳ 🛠 tv-sim	~~🧪 mac-wk2-stress~~
	⏳ 🛠 watch
	⏳ 🛠 watch-sim

webkit-early-warning-system · 2024-01-30T01:10:18Z

EWS run on previous version of this PR (hash 11e865f)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	⏳ 🛠 wincairo
✅ 🧪 bindings	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	⏳ 🧪 wpe-wk2
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	✅ 🧪 api-mac	✅ 🧪 api-wpe
	⏳ 🧪 ios-wk2-wpt	❌ 🧪 mac-wk1	✅ 🛠 gtk
⏳ 🛠 🧪 jsc	✅ 🧪 api-ios	❌ 🧪 mac-wk2	~~🧪 gtk-wk2~~
	✅ 🛠 tv	⏳ 🧪 mac-AS-debug-wk2	✅ 🧪 api-gtk
	⏳ 🛠 tv-sim
	⏳ 🛠 watch
	✅ 🛠 watch-sim

alanbaradlay · 2024-01-30T01:13:42Z

Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp

+std::optional<size_t> InlineFormattingContext::numberOfVisibleLinesAllowed() const
+{
+    if (auto lineClamp = layoutState().parentBlockLayoutState().lineClamp())
+        return lineClamp->maximumLineCount > lineClamp->currentLineCount ? lineClamp->maximumLineCount - lineClamp->currentLineCount : 0;
+    return { };
+}


any particular reason why this has to be on InlineFormattingContext now?

It's just that this is already calculated at InlineFormattingContext::createDisplayContentForInlineContent, so I wanted to reuse it (Which I forgot to do in this patch).

please don't. InlineFormattingContext's API should stay focused. if you are interested in sharing code, move it to a helper function to the util class but I don't think it's worth the effort.

alanbaradlay · 2024-01-30T01:15:59Z

Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.cpp

+    if (!m_inlineFormattingContext.layoutState().placedFloats().isEmpty() || numberOfVisibleLinesAllowed == 1) {
        m_cannotBalanceContent = true;


I think this is quite misleading and somewhat error prone. numberOfVisibleLinesAllowed == 1 means we should not balance which is very different from cannot. -even if InlineContentBalancer currently ends up doing the same for both cases.

Agree. I've almost changed the name to shouldNotBalanceContent. I guess I'll do it. I assume that "should not" also makes sense for the case we just to avoid balancing for floats until it is unsupported.

alanbaradlay · 2024-01-30T01:17:06Z

Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.h

@@ -62,6 +62,7 @@ class InlineFormattingContext {
    std::pair<LayoutUnit, LayoutUnit> minimumMaximumContentSize(const InlineDamage* = nullptr);
    LayoutUnit minimumContentSize(const InlineDamage* = nullptr);
    LayoutUnit maximumContentSize(const InlineDamage* = nullptr);
+    std::optional<size_t> numberOfVisibleLinesAllowed() const;


this should somehow reference to line-clamp to make it clear where this constrain comes from

webkit-early-warning-system · 2024-01-30T05:25:21Z

Starting EWS tests for 229d01e. Live statuses available at the PR page, #23479

webkit-early-warning-system · 2024-01-30T05:25:21Z

EWS run on previous version of this PR (hash 229d01e)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	✅ 🛠 wincairo
✅ 🧪 bindings	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	✅ 🧪 wpe-wk2
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	✅ 🧪 api-mac	✅ 🧪 api-wpe
	✅ 🧪 ios-wk2-wpt	✅ 🧪 mac-wk1	✅ 🛠 gtk
⏳ 🛠 🧪 jsc	✅ 🧪 api-ios	✅ 🧪 mac-wk2	✅ 🧪 gtk-wk2
	✅ 🛠 tv	✅ 🧪 mac-AS-debug-wk2	✅ 🧪 api-gtk
	✅ 🛠 tv-sim
	✅ 🛠 watch
	✅ 🛠 watch-sim

alanbaradlay · 2024-01-30T15:33:42Z

Source/WebCore/layout/formattingContexts/inline/InlineFormattingUtils.cpp

@@ -569,6 +569,13 @@ const InlineLayoutState& InlineFormattingUtils::layoutState() const
    return formattingContext().layoutState();
 }

+std::optional<size_t> InlineFormattingUtils::numberOfVisibleLinesAfterLineClamping() const


what does "after line clamping" mean here?

Hmmm, yeah, maybe it's not the best name. How about "numberOfVisibleLinesConsideringLineClamping"? I'm also open for suggestions of course!

webkit-early-warning-system · 2024-01-30T17:55:25Z

Starting EWS tests for 09d86a1. Live statuses available at the PR page, #23479

webkit-early-warning-system · 2024-01-30T17:55:25Z

EWS run on previous version of this PR (hash 09d86a1)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	✅ 🛠 wincairo
✅ 🧪 bindings	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	✅ 🧪 wpe-wk2
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	✅ 🧪 api-mac	✅ 🧪 api-wpe
	✅ 🧪 ios-wk2-wpt	✅ 🧪 mac-wk1	✅ 🛠 gtk
⏳ 🛠 🧪 jsc	✅ 🧪 api-ios	✅ 🧪 mac-wk2	✅ 🧪 gtk-wk2
	✅ 🛠 tv	✅ 🧪 mac-AS-debug-wk2	✅ 🧪 api-gtk
	✅ 🛠 tv-sim
	✅ 🛠 watch
	✅ 🛠 watch-sim

alanbaradlay · 2024-01-30T18:37:29Z

Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp

-    auto numberOfVisibleLinesAllowed = [&] () -> std::optional<size_t> {
-        if (auto lineClamp = layoutState().parentBlockLayoutState().lineClamp())
-            return lineClamp->maximumLineCount > lineClamp->currentLineCount ? lineClamp->maximumLineCount - lineClamp->currentLineCount : 0;
-        return { };
-    }();
+    auto numberOfVisibleLinesConsideringLineClamp = formattingUtils().numberOfVisibleLinesConsideringLineClamp();


diff --git a/Source/WebCore/layout/formattingContexts/block/BlockLayoutState.h b/Source/WebCore/layout/formattingContexts/block/BlockLayoutState.h index b3eb317d69f1..f59cdee0b941 100644 --- a/Source/WebCore/layout/formattingContexts/block/BlockLayoutState.h +++ b/Source/WebCore/layout/formattingContexts/block/BlockLayoutState.h @@ -37,6 +37,8 @@ class BlockFormattingContext; class BlockLayoutState { public: struct LineClamp { + size_t allowedLineCount() const { return std::max(maximumLineCount - currentLineCount, 0lu); } + size_t maximumLineCount { 0 }; size_t currentLineCount { 0 }; }; diff --git a/Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp b/Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp index 23a98ec5d724..df2a13e72dd6 100644 --- a/Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp +++ b/Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp @@ -345,11 +345,7 @@ void InlineFormattingContext::updateBoxGeometryForPlacedFloats(const LineLayoutR InlineRect InlineFormattingContext::createDisplayContentForInlineContent(const LineBox& lineBox, const LineLayoutResult& lineLayoutResult, const ConstraintsForInlineContent& constraints, InlineDisplay::Content& displayContent, size_t numberOfPreviousLinesWithInlineContent) { - auto numberOfVisibleLinesAllowed = [&] () -> std::optional<size_t> { - if (auto lineClamp = layoutState().parentBlockLayoutState().lineClamp()) - return lineClamp->maximumLineCount > lineClamp->currentLineCount ? lineClamp->maximumLineCount - lineClamp->currentLineCount : 0; - return { }; - }(); + auto numberOfVisibleLinesAllowed = layoutState().parentBlockLayoutState().lineClamp() ? std::make_optional(layoutState().parentBlockLayoutState().lineClamp()->allowedLineCount()) : std::nullopt;

Maybe something like this would work and then you don't have to think about name at all (no util function is needed)

alanbaradlay · 2024-01-30T18:42:00Z

Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.cpp

+    if (!m_inlineFormattingContext.layoutState().placedFloats().isEmpty() || numberOfVisibleLinesConsideringLineClamp == 1) {
+        m_shouldNotBalanceContent = true;
        return;


What I really meant here was that there's a difference between cases when we bail out due to unable to balance (floats are present) and cases when there's only one line and we can take a fast path. InlineContentBalancer may not care about the difference yet but I think it would make the code read better if we decoupled these 2.

alanbaradlay · 2024-01-30T18:47:30Z

Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.cpp

+        if (numberOfVisibleLinesConsideringLineClamp && lineIndex >= numberOfVisibleLinesConsideringLineClamp)
+            break;


nit: you can bail out a lot earlier.

Don't we have to initialize the Balancer until we would reach the last line before clamping?

when you say Balancer are you referring to InlineContentBalancer? -just wanna make sure we are talking about the same thing.

Yes, exactly!

ok, yes we have to initialize the InlineContentBalancer, but we are inside InlineContentBalancer. What I was trying to say with my original comment was please look and make sure we don't compute anything redundant here (i.e. perhaps moving this check a few lines above? -maybe "a lot earlier" was a bit of an exaggeration)

webkit-early-warning-system · 2024-01-31T00:09:51Z

Starting EWS tests for c0b6d04. Live statuses available at the PR page, #23479

webkit-early-warning-system · 2024-01-31T00:09:51Z

EWS run on previous version of this PR (hash c0b6d04)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	⏳ 🛠 wincairo
✅ 🧪 bindings	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	⏳ 🧪 wpe-wk2
✅ 🧪 webkitperl	~~🧪 ios-wk2~~	✅ 🧪 api-mac	✅ 🧪 api-wpe
	⏳ 🧪 ios-wk2-wpt	✅ 🧪 mac-wk1	✅ 🛠 gtk
⏳ 🛠 🧪 jsc	~~🧪 api-ios~~	✅ 🧪 mac-wk2	⏳ 🧪 gtk-wk2
⏳ 🛠 🧪 jsc-arm64	⏳ 🛠 tv	⏳ 🧪 mac-AS-debug-wk2	⏳ 🧪 api-gtk
	⏳ 🛠 tv-sim
	⏳ 🛠 watch
	✅ 🛠 watch-sim

alanbaradlay · 2024-01-31T00:30:29Z

Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp

-    auto numberOfVisibleLinesAllowed = [&] () -> std::optional<size_t> {
-        if (auto lineClamp = layoutState().parentBlockLayoutState().lineClamp())
-            return lineClamp->maximumLineCount > lineClamp->currentLineCount ? lineClamp->maximumLineCount - lineClamp->currentLineCount : 0;
-        return { };
-    }();
+    auto numberOfVisibleLinesConsideringLineClamp = layoutState().parentBlockLayoutState().lineClamp() ? std::make_optional(layoutState().parentBlockLayoutState().lineClamp()->allowedLineCount()) : std::nullopt;


do you mind keeping the current variable name? While it was not great as a function name (no context in the header) I think it's fine as a variable name here.

webkit-early-warning-system · 2024-01-31T00:45:03Z

EWS run on current version of this PR (hash 867f21f)

Misc	iOS, tvOS & watchOS	macOS	Linux	Windows
✅ 🧪 style	✅ 🛠 ios	✅ 🛠 mac	✅ 🛠 wpe	~~🛠 wincairo~~
✅ 🧪 bindings	✅ 🛠 ios-sim	✅ 🛠 mac-AS-debug	~~🧪 wpe-wk2~~
✅ 🧪 webkitperl	✅ 🧪 ios-wk2	~~🧪 api-mac~~	~~🧪 api-wpe~~
	~~🧪 ios-wk2-wpt~~	~~🧪 mac-wk1~~	✅ 🛠 gtk
	✅ 🧪 api-ios	~~🧪 mac-wk2~~	~~🧪 gtk-wk2~~
	~~🛠 tv~~	~~🧪 mac-AS-debug-wk2~~	~~🧪 api-gtk~~
	~~🛠 tv-sim~~
✅ 🛠 🧪 merge	~~🛠 watch~~
	✅ 🛠 watch-sim

https://bugs.webkit.org/show_bug.cgi?id=268302 rdar://121858978 Reviewed by Alan Baradlay. According to spec resolution [1], if line-clamp is defined, text-wrap: balance should balance only within the clamped lines. Up to this patch, we would balance taking into consideration all the lines and we would clamp it after balance. This patches makes InlineContentBalancer::initialize() take the maximum number of visible lines into account, based into the line-clamp property. Also, this allows for a small optimization: If line-clamp clamps to 1 line, we can skip balacing. [1] w3c/csswg-drafts#9310 * LayoutTests/TestExpectations: * Source/WebCore/layout/formattingContexts/block/BlockLayoutState.h: (WebCore::Layout::BlockLayoutState::LineClamp::allowedLineCount const): * Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.cpp: (WebCore::Layout::InlineContentBalancer::initialize): (WebCore::Layout::InlineContentBalancer::computeBalanceConstraints): * Source/WebCore/layout/formattingContexts/inline/InlineContentBalancer.h: * Source/WebCore/layout/formattingContexts/inline/InlineFormattingContext.cpp: (WebCore::Layout::InlineFormattingContext::createDisplayContentForInlineContent): Canonical link: https://commits.webkit.org/273800@main

webkit-commit-queue · 2024-01-31T01:28:38Z

Committed 273800@main (c1353df): https://commits.webkit.org/273800@main

Reviewed commits have been landed. Closing PR #23479 and removing active labels.

rkirsling · 2024-01-31T02:26:35Z

Looks like this patch doesn't build on Windows.

alanbaradlay · 2024-01-31T03:33:48Z

Looks like this patch doesn't build on Windows.

revert?

vitorroriz · 2024-01-31T03:38:09Z

Looks like this patch doesn't build on Windows.

revert?

Let me see...

vitorroriz · 2024-01-31T03:40:42Z

Interesting, 09d86a1 version of this patch was building for Windows, so I haven't paid much attention on that on the new iteration. Can you, please, provide me the build error you are seeing @rkirsling ?

vitorroriz · 2024-01-31T03:47:54Z

Ops, nevermind it. I found it on the windows pipeline.

vitorroriz · 2024-01-31T04:21:29Z

#23560

vitorroriz self-assigned this Jan 30, 2024

vitorroriz added the CSS Cascading Style Sheets implementation label Jan 30, 2024

vitorroriz force-pushed the text-wrap-balance-line-clamp branch from b4d42f2 to 11e865f Compare January 30, 2024 01:03

alanbaradlay reviewed Jan 30, 2024

View reviewed changes

webkit-ews-buildbot added the merging-blocked Applied to prevent a change from being merged label Jan 30, 2024

vitorroriz removed the merging-blocked Applied to prevent a change from being merged label Jan 30, 2024

vitorroriz changed the title ~~text-wrap balance should consider line-clamp when balacing~~ text-wrap balance should consider line-clamp when balancing Jan 30, 2024

vitorroriz force-pushed the text-wrap-balance-line-clamp branch from 11e865f to 229d01e Compare January 30, 2024 05:24

vitorroriz requested a review from alanbaradlay January 30, 2024 05:27

alanbaradlay reviewed Jan 30, 2024

View reviewed changes

vitorroriz force-pushed the text-wrap-balance-line-clamp branch from 229d01e to 09d86a1 Compare January 30, 2024 17:55

alanbaradlay reviewed Jan 30, 2024

View reviewed changes

vitorroriz force-pushed the text-wrap-balance-line-clamp branch from 09d86a1 to c0b6d04 Compare January 31, 2024 00:09

vitorroriz requested a review from alanbaradlay January 31, 2024 00:15

alanbaradlay approved these changes Jan 31, 2024

View reviewed changes

vitorroriz force-pushed the text-wrap-balance-line-clamp branch from c0b6d04 to 867f21f Compare January 31, 2024 00:44

vitorroriz added the merge-queue Applied to send a pull request to merge-queue label Jan 31, 2024

webkit-commit-queue force-pushed the text-wrap-balance-line-clamp branch from 867f21f to c1353df Compare January 31, 2024 01:28

webkit-commit-queue merged commit c1353df into WebKit:main Jan 31, 2024

webkit-commit-queue removed the merge-queue Applied to send a pull request to merge-queue label Jan 31, 2024

		if (!m_inlineFormattingContext.layoutState().placedFloats().isEmpty() \|\| numberOfVisibleLinesAllowed == 1) {
		m_cannotBalanceContent = true;

		if (numberOfVisibleLinesConsideringLineClamp && lineIndex >= numberOfVisibleLinesConsideringLineClamp)
		break;

text-wrap balance should consider line-clamp when balancing #23479

text-wrap balance should consider line-clamp when balancing #23479

Uh oh!

Conversation

vitorroriz commented Jan 30, 2024 • edited by webkit-early-warning-system Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

webkit-early-warning-system commented Jan 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

webkit-early-warning-system commented Jan 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

webkit-early-warning-system commented Jan 30, 2024

Uh oh!

webkit-early-warning-system commented Jan 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vitorroriz Jan 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

webkit-early-warning-system commented Jan 30, 2024

Uh oh!

webkit-early-warning-system commented Jan 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

webkit-early-warning-system commented Jan 31, 2024

Uh oh!

webkit-early-warning-system commented Jan 31, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

webkit-early-warning-system commented Jan 31, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

webkit-commit-queue commented Jan 31, 2024

Uh oh!

rkirsling commented Jan 31, 2024

Uh oh!

alanbaradlay commented Jan 31, 2024

Uh oh!

vitorroriz commented Jan 31, 2024

Uh oh!

vitorroriz commented Jan 31, 2024

Uh oh!

vitorroriz commented Jan 31, 2024

Uh oh!

vitorroriz commented Jan 31, 2024

Uh oh!

Uh oh!

vitorroriz commented Jan 30, 2024 •

edited by webkit-early-warning-system

Loading

webkit-early-warning-system commented Jan 30, 2024 •

edited

Loading

webkit-early-warning-system commented Jan 30, 2024 •

edited

Loading

webkit-early-warning-system commented Jan 30, 2024 •

edited

Loading

vitorroriz Jan 30, 2024 •

edited

Loading

webkit-early-warning-system commented Jan 30, 2024 •

edited

Loading

webkit-early-warning-system commented Jan 31, 2024 •

edited

Loading

webkit-early-warning-system commented Jan 31, 2024 •

edited

Loading