Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to Firefox v118 / Playwright 1.40 #183

Merged
10,000 commits merged into from
Jan 10, 2024
Merged

Update to Firefox v118 / Playwright 1.40 #183

10,000 commits merged into from
Jan 10, 2024

Conversation

tmbrbr
Copy link
Contributor

@tmbrbr tmbrbr commented Jan 9, 2024

This PR merges the Firefox upstream branch to v118, corresponding to Playwright patches v1.40

https://github.com/microsoft/playwright/blob/release-1.40/browser_patches/firefox/UPSTREAM_CONFIG.sh

This will fix #182

AdamBrouwersHarries and others added 30 commits August 25, 2023 13:19
This patch adds an API to count the number of restyles triggered by animations. This API will replace the existing timeline marker based testing of the animation/restyle system.

Differential Revision: https://phabricator.services.mozilla.com/D186714
…legate methods r=geckoview-reviewers,willdurand,owlish,amejiamarmol

Differential Revision: https://phabricator.services.mozilla.com/D184071
…r. r=smaug

See bug 1404916 comment 1. This should improve that, though we should
still try to remove this hack, probably.

Differential Revision: https://phabricator.services.mozilla.com/D186700
…s r=emilio

This commits integrates the new animation triggered restyle counter into the existing tests to ensure that the counter matches the expected marker count.

Depends on D186714

Differential Revision: https://phabricator.services.mozilla.com/D186715
…ILD CLOSED TREE

es-CL -> 5b9636398268a349fa80df106e7732733e54c0e0
fur -> b37a9e661ec05bc8f2dd4340587dbc4b4f052fd9
fy-NL -> 3ee65a7e68d78806ee3cebcac13abbb1c1784aa1
kab -> 7c632346288f3cf612d73d627f080281a5d60a58
kk -> 253943111f7cc3d6d29ff9fa157b5decd17cdb99
ro -> daa5c61f5590c9284d39eecd07ea3d4398c2b54a
sk -> f216ff296dac34c66478c66487d69a70be9cb368
… in XPCOMShutdown or later. r=gfx-reviewers,aosmond

XPCOMShutdownThreads is the phase just after XPCOMShutdown and XPCOMShutdown is when we destory the ImageBitmapShutdownObserver, so we need to not create a new ImageBitmapShutdownObserver if we are in XPCOMShutdown or later.

Differential Revision: https://phabricator.services.mozilla.com/D186852
…s,aosmond

I don't quite understand why this fixes the problem but it's
obviously more correct.

Differential Revision: https://phabricator.services.mozilla.com/D186869
This updates aa-stroke to fef8702c4c8afd7d47e7a5aafb6fa347c96b50be
which fixes some degenerate behaviour when mitering parallel lines.

Differential Revision: https://phabricator.services.mozilla.com/D186859
…es at browser_test_group_fission.js CLOSED TREE
…ILD CLOSED TREE

en-GB -> 4a167a105945e57ff848f081b1cb35145590f890
eo -> aeb33cd0813057db6f18d9d980c37939c50edf7c
…ILD CLOSED TREE

nn-NO -> 9f8bf1fe9b080c0383c9e4de91e39b881c30f404
ru -> cb4082d60d984a71ad5ba88de642e79da9d27b89
sat -> ec48d950e2bd21fa926d91d739992e7786015b37
vi -> 9efe9e262cf06dd782813ad15c924edd1e0c3efc
zh-CN -> 56971e217d0204c7dff6052db727b84205c51596
…ull-size-kana mapping. r=dholbert

Testing: there's a new WPT (text-transform-full-size-kana-008.html) coming from upstream that will cover this.

Note that the current version of the test, just landed in WPT, has a typo that will cause it to fail if it merges
in its current form. I've left a comment on the WPT commit to get this corrected:
web-platform-tests/wpt@3412a27#r125601740)

Differential Revision: https://phabricator.services.mozilla.com/D186883
… because CSS Page Orientation is disabled there.

Bug 1833244 added sheet rotation support. The test depends on CSS Page
Orientation only enabled in Nightly, controlled by the preference
layout.css.page-orientation.enabled.

Differential Revision: https://phabricator.services.mozilla.com/D186723
…ILD CLOSED TREE

it -> e4f5963fb1cd3ec8da5abd93d9298ae020dd8d9d
nn-NO -> eb3922f34ef6201b15bd83671b73fb68597d24bc
…ILD CLOSED TREE

cs -> b1267386551026cf1921a30ffb177e2509eaa270
eu -> 2ad125fb918991d0eb255dbb9555bd3465cf5730
si -> 634ad5c8848e28cb4ad60f4023db61ae7207f307
sk -> 0818fe1dfcaf179aeaf3118314cf15e42a53e467
sv-SE -> 30c0048cb7d864e4224fca94b70c532533d8da00
vi -> 79dbed19041865ca1bd7e6a7b0391720a7ff07f2
…X_BETA_118_BASE a=release DONTBUILD CLOSED TREE
Pehrsons and others added 24 commits September 15, 2023 17:46
…rmuizel a=pascalc

This issue was originally reported by Asahi Lina, and they also proposed the original
version of these changes. I have reworked them a bit just to clean up how clip TCs
are passed down so that distance AA does not have to be highp.

Their original comment describing the issue were, in part:

"See DrawTargetWebgl::SharedContext::CreateShaders in dom/canvas/DrawTargetWebgl.cpp. The fragment shaders specify precision mediump float; and then don't use overriding precision qualifiers anywhere. This causes the texcoords to use fp16 precision on GPUs that support it, which is not sufficient for correct rendering."

"Note that this is a common mistake and the Mesa GPU driver we've been developing actually includes a heuristic that fixes the first instance of the problem (where the varying is used as a texcoord directly), but not the second one where there is an intermediate clamp(). It is that second one that is breaking Google Sheets."

Differential Revision: https://phabricator.services.mozilla.com/D187694
br -> 19b13cb7767c0c114fe03b8f3be1ecfaddc26826
da -> c3dba3ea996b745c42fd0477d60d7d277bcc17de
en-CA -> 3694b22a261d8d09a064356a78293d14b13b0350
en-GB -> e6f333c18c80fbc0f5bb2562a876565e879fd57d
es-AR -> 7d5eb75c0ff26e59b36f2792c52904bb242dd161
fi -> b5670076eed74b004348982baf0095df51dfe3e2
fy-NL -> 99aa8af2e5ab0823483dd2f6abbdd66b7b3507cf
gn -> 13f1a36cba827ea6a74e89c66bcfbd11170af621
he -> 97badfc65571614917056d877a0df236767ead08
hsb -> 0fa97645cb2663ffa8079222dce5eaccfce6c48c
hu -> ff57bd462e7491cfbb6c8a925a1b68326fb8200b
it -> 3df1319eb89dbb2a69f71fa2e5627fcf4676d75c
nn-NO -> 345298286538e5ce74aaf9e9abf1646bf8eab1b6
pa-IN -> 78756d9f50f6251175fd1fc02b91515826351037
pt-BR -> 9aa923dae904af3eb7148638e947ce5939df3fb4
sk -> e422317951d705d5e26a327fec1474dce2d53c17
tr -> 4ecfeb048c0a71484304da569b9bea2a266ad738
uk -> 787c6a473444a110430c12b7e32e706c6067f925
…RenderedTextureHost r=gfx-reviewers,lsalzman a=pascalc

mLatestRenderedTextureHost could block remote textures recycling when mLatestRenderedTextureHost is last compositable ref of remote texture's TextureHost.

When remote textures were pushed but they were not rendered, mLatestRenderedTextureHost was not updated. But size of mUsingTextureDataHolders were increased. Since remote textures are recycled as FIFO order. If mLatestRenderedTextureHost is not updated, front of mUsingTextureDataHolders is not recycled.

The patch unblocks remote texture recyclieng in this case.

Differential Revision: https://phabricator.services.mozilla.com/D188163
dsb -> 37a9bcae23386874dff36f55fc5de9062a27ae02
es-AR -> 13f3cfadf7afa5f6f3c9e5fb424ae753573c6093
gn -> fdc5df0db43e8046444d887d0941e084f5323666
hsb -> 78ed792b1b99e91a4531cc6b358dd57658964adf
hu -> 9cd5cade583377b66b8fe69b7c5da76eafacfaf6
it -> e5ffb780102705d9c4dd0383e5af1b9ad6f76beb
ka -> c0cfda1114cc4f6714049593442ed37c157da5e2
nb-NO -> 5f8938422913567180a6ccb29f19736fe3f09aa1
nn-NO -> d346915ada79c68797e29e5b506bbe489ed01073
pa-IN -> 3764e815775452afa7f3e3a88e3bb36d66f6fdbf
pt-PT -> 532aba2b25f108a2070f984385d50017dd2a7c6c
ru -> 766c31aca5e2b9f083b01a7500d575e661d29f4a
tg -> 31e6cffe3232327162cbcdf4fc71999bfe8f1b68
uk -> 2ec3552cf91096bbb77fa864e58cafa709171499
vi -> 428f44bc6591f6373536e8976a4a57376912ca50
be -> c8dcebb8ce19d841d2d4f3e6d311bd8f44920bda
dsb -> ee61b0159c3ffb76d3937a0c02ab8cbaeef163d8
fi -> 7f4d3de8051d7b104006503e4a5b0b235ef10327
hsb -> 56c18f58383751ec2ad8cea3cfb9a4d3a123e156
kk -> 261a9f070e19f80836bb55888305e5a3abb60ebe
nb-NO -> b1ebea7053529b38f8d325fa1232a619541434d8
nn-NO -> a558dc45f8f884141bc701d25717356839a9a7f0
pa-IN -> 3bc68857a78b38731e46d83083a6ce013a9b56e3
pl -> b772a36abe5365ce39fcf6fce5ca1507f0abaa13
rm -> c1ff0404de2a4f01e3c95be1b3f88acc7d98f3cf
tg -> 42e854499c907365e30d40985106ab90fa7e7ced
uk -> 7b33b3d08951420f838590cea469fa8990ab53e5
…X_RELEASE_118_BASE a=release DONTBUILD CLOSED TREE
…6f98c65b90 852ec20a6a1d55bfe81b5a8e24c2d2c9a77891ed| CLOSED TREE DONTBUILD a=release
…X_RELEASE_117_END a=release DONTBUILD CLOSED TREE
…X_118_0_BUILD1 a=release CLOSED TREE DONTBUILD
…X_118_0_RELEASE a=release CLOSED TREE DONTBUILD
@tmbrbr tmbrbr marked this pull request as draft January 9, 2024 16:18
@tmbrbr tmbrbr self-assigned this Jan 9, 2024
@tmbrbr tmbrbr added the upstream Issue related to upstream Firefox label Jan 9, 2024
Copy link

cla-assistant bot commented Jan 9, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 22 committers have signed the CLA.

✅ tmbrbr
❌ Mozilla Releng Treescript
❌ iainireland
❌ stransky
❌ emilio
❌ gregtatum
❌ mikeconley
❌ brennie
❌ tnikkel
❌ padenot
❌ bradwerth
❌ jesup
❌ CosminSabou
❌ mkmelin
❌ nordzilla
❌ lsalzman
❌ rvandermeulen
❌ daleharvey
❌ bobowen
❌ jmaher
❌ groovecoder
❌ Pehrsons


Mozilla Releng Treescript seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@tmbrbr tmbrbr marked this pull request as ready for review January 10, 2024 08:27
@tmbrbr tmbrbr closed this pull request by merging all changes into SAP:main in d9f74c7 Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Issue related to upstream Firefox
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update to Playwright v1.40