Adding upstream version 115.7.0esr.upstream/115.7.0esrupstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 48 insertions, 0 deletions

diff --git a/testing/web-platform/tests/fledge/tentative/TODO b/testing/web-platform/tests/fledge/tentative/TODO
new file mode 100644
index 0000000000..d50e492611
--- /dev/null
+++ b/testing/web-platform/tests/fledge/tentative/TODO
@@ -0,0 +1,48 @@
+Need tests for (likely not a complete list):
+
+* directFromSellerSignals.
+* All generateBid() and scoreAd() input parameters.
+* All interest group fields (passed to auction, have effect on auction).
+    Validation when joining/leaving interest group is already covered.
+* Filtering/prioritization (including bidding signals influencing priorities)
+* Size restrictions.
+* Updates (both after auction and triggered).
+* All auctionConfig parameters (including invalid auctionConfigs, and ones
+    with no buyers).
+* Interest group expiration.
+* Multiple buyers.
+* Multiple interest group with same owner.
+* Multiple origin auctions (buyer != publisher != seller).
+* Multiple frame tests (including join IG policy, run auction policy,
+    loading URNs in fencedframes in other frames, loading component
+    ad URNs in fenced frames of other frames, etc)
+* adAuctionConfig passed to reportResult().
+* trusted scoring signals.
+* Component ads.
+* Component auctions.
+* browserSignals fields in scoring/bidding methods.
+* In reporting methods, browserSignals fields: dataVersion, topLevelSeller,
+    componentSeller, modifiedBid, adCost, madeHighestScoringOtherBid
+    (with interest group from another origin).
+* Loading ads in iframes.
+* In fencedframes window.fence.setReportEventDataForAutomaticBeacons()
+* Calling leaveAdInterestGroup() in the frame of a winning ad (and one
+    of its component ads)
+* Network timeouts.
+* Validate specific escaping behavior logic (still under discussion). There
+    are a number of different rules for which characters are escaped, and
+    whether spacess are escaped as "%20" or "+".
+* Reports not sent if ad not used.
+* Ties.
+* Interactions with local network access API, which requires public
+    networks to send CORS preflights for requests made over local networks.
+    Needs testing with public publisher pages running auctions with
+    sellers / buyers / update URLs on local networks.
+
+If possible:
+* Aggregate reporting.
+* Join/leave permission delegation via .well-known files.
+* k-anonymity.
+* Signals request batching. This is an optional feature, so can't require it,
+    but maybe a test where batching could be used, and make sure things work,
+    whether batching is used or not?