Correction for the original PSA that this bug fix was enabled in 132
instead of 131.
https://chromiumdash.appspot.com/commit/e16c86f61d100d488770da8efa5d4ac28bc0e8a4
On Wednesday, October 16, 2024 at 1:25:36 PM UTC-4 Di Zhang wrote:
> I couldn't find one, so I created:
> https://bugs.webkit.org
I couldn't find one, so I
created: https://bugs.webkit.org/show_bug.cgi?id=281587
Thanks!
On Tuesday, October 15, 2024 at 6:25:05 PM UTC-7 dan...@microsoft.com wrote:
> *> **WebKit**: No signal Webkit has this bug, since this has existed for
> a long time.*
>
> Is there a bug filed in their iss
> WebKit: No signal Webkit has this bug, since this has existed for a long time.
Is there a bug filed in their issue tracker for this? If not maybe you could
file one and see if there’s willingness on their side to fix it? It would be
nice if there was alignment here since the current behavior i
