Automatic update from web-platform-tests
Move CORS logic from direct-from-seller-signals.py to fledge_http_server_util.py
The CORS logic present in direct-from-seller-signals.py is identical to
that needed for other web platform tests. Moving this logic into a
common function available to the endpoints needed for those other web
platform tests prevents duplication. This change also attempts to match
the style of the Python test server in new and existing code.
Change-Id: Ia3db1e263e3e4b1e6b09bfa3408dd905a83ea44b
Bug: 40275797
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5269747
Commit-Queue: Orr Bernstein <orrb@google.com>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1256845}
--
wpt-commits: 516158d4bdc86c5de892cc75355841f478999b71
wpt-pr: 44412
Automatic update from web-platform-tests
[css-scroll-snap-2] Prioritize focused snap targets
An agreed upon proposal[1] by the CSS working group specifies that
where multiple scroll snap targets are visually equally aligned,
scroll containers should give priority to focused elements.
Blink did this for programmatic scrolls but not for user scrolls.
This patch prioritizes focused elements for both types of scrolls
by relying on a bit in SnapAreaData.
[1]https://github.com/w3c/csswg-drafts/issues/9622
Bug: 1523819
Change-Id: I81e2aaf0845e9763abb463a960614beb37b05a8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5255777
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1256790}
--
wpt-commits: d56b1391cbf0979b0f333a1cae23875acb06be1b
wpt-pr: 44338
Automatic update from web-platform-tests
Improve reflected attribute tests (html/dom/reflection.js)
* Fix reflection tests wrt valueOf
Without a toString:null in test values that are objects
with a valueOf method, the DOM attribute would actually
be set to "[object Object]" without ever calling the
valueOf method (effectively turning those tests into
behaving exactly the same as the {"test": 6} ones).
Most existing tests were passing because the implemented
algorithms would actually compute a WRONG expected value.
The only test that doesn't compute the expected value
("double") won't actually run because all reflected IDL
attributes of type "double" have custom getters.
Fixes#44315
* Fix reflection tests wrt -0 for "double" attributes
Setting -0 to the IDL attribute will set the DOM
attribute to "0" (per ECMAScript's ToString, from the
rules for the the best representation of a number as
a floating point number), and the rules for parsing
flowting-point number values won't ever turn that "0"
into a -0 value.
This test value is never actually being used though,
as all the reflected attributes of type "double" have
custom getters.
* Add a few more reflection tests around whitespace for numeric types
Specifically leading non-ASCII whitespace following leading
ASCII whitespace (should be rejected), and trailing non-ASCII
whitespace (should be ignored)
* Add a few more numeric values to reflection tests
Specifically "+" and "-" to exercise all possible code
paths of failures.
* Add exponential notation to reflection tests of double values
* Implement "limited double" in reflection tests
* Implement the reflect algorithm for doubles
This should make it easier to extend tests with more values.
--
wpt-commits: cdafbec95bd598d0bd109e1210053dfe664e6901
wpt-pr: 44355
Automatic update from web-platform-tests
html: Tests for field-sizing (#44346)
This includes tests to confirm size/cols/rows are not presentational hints.
Issue: https://github.com/whatwg/html/issues/6807
--
wpt-commits: df6595ec7e75fdf8fb524a039c32a030fc1075e9
wpt-pr: 44346
Automatic update from web-platform-tests
Support :user-valid/:user-invalid on checkboxes
Checkboxes support validity via the required attribute and the other
browsers support :user-valid/:user-invalid on them. The existing
:user-valid/:user-invalid machinery only works on text fields, so this
patch adds some code to checkboxes to make them work as well.
Fixed: 1521781
Change-Id: I91309f36348470db5b1c706b519e6303e5deeab1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5258739
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1256264}
--
wpt-commits: 81c06c7deb8241aa22d39f5f7fffbe33c555bf34
wpt-pr: 44354
Automatic update from web-platform-tests
[A11y] Do not include hidden nodes when they are ignored
The only time we need hidden nodes is when they are part of a
label or description. This CL keeps track of whether a given node
has ever been part of a label or description. If the node is hidden,
it removes it from the tree unless it's needed for a label/description.
In combination with CL:4852390, which removes hidden line breaks,
reduces the time spent in serialization and deserialization by
massive amounts in tests that involve heavy usage of hidden subtrees.
For the specific results, see:
https://docs.google.com/spreadsheets/d/1ozLJMRT32yIxE0ja0rDhdZPb76hQtDd0klcRcR_uWYU/edit?pli=1#gid=0
This will make a significant difference in web apps with panels,
chats, slides, etc. where a significant percentage of the content
is hidden.
Bug: 1448706, 1353788
Cq-Include-Trybots: luci.chromium.try:fuchsia-x64-accessibility-rel,linux-blink-web-tests-force-accessibility-rel
Change-Id: I1b0de1d9b6f037c107efd3ca93c073382fd0ece1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4574033
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1256230}
--
wpt-commits: 83ca3f916e893dbdc3cfaa498aa10fc5674ed006
wpt-pr: 43095
Automatic update from web-platform-tests
Add test for console logging a Symbol
Signed-off-by: syvb <me@iter.ca>
--
wpt-commits: d0a66dfb73bb3925157f4768beee24d30d73f355
wpt-pr: 44342
When RenderDXGITextureHost has keyed mutex, RenderDXGITextureHost::SyncObjectNeeded() should return false. But RenderDXGITextureHost::SyncObjectNeeded() return true. Then the Synchronize() is called when it is not necessary
Differential Revision: https://phabricator.services.mozilla.com/D201674
There are two types of config in Rust Suggest: global and per-provider. Right
now global contains `show_less_frequently_cap`, and the only provider config is
for weather, which contains `min_keyword_length`. This patch uses both of them.
It makes sense to me to fetch config as part of the ingest process, so that's
what I've done. I'm not sure when else would be a good time. It's async so it's
not too convenient to do it on demand.
In RS records and attachement JSON, we use snake_case, but Rust converts it to
camelCase (actually UniFFI does, I think). That means the JS backend will use
snake_case for all config, but the Rust backend will use camelCase. I wrote a
helper for converting snake to camel so we can always just use camel.
Depends on D200755
Differential Revision: https://phabricator.services.mozilla.com/D201023
This reverts commit e25a5f344af32bdd689500bae7b4f24f205ba9f0.
We believe bug 1664063 was causing to hit some broken device reset
handling code.
Differential Revision: https://phabricator.services.mozilla.com/D201658
clang 19 is making -Wshorten-64-to-32 enabled by
-Wimplicit-int-conversion. This returns to the error level we could
handle up to clang 18.
Differential Revision: https://phabricator.services.mozilla.com/D201194
Using a background for text color is not great.
Provide a text color to draw on top of the toolbarbutton-icon-attention
color.
Differential Revision: https://phabricator.services.mozilla.com/D201202
The change suppresses the clang-tidy warning. This patch doesn't change
the behavior in the release. However, if overflow happens, the
assertions will be triggered in nightly and beta.
Depends on D200887
Differential Revision: https://phabricator.services.mozilla.com/D201610