← back to v134 · attribution-reporting-feature-remove-aggregatable-report-limit-when-trigger-cont
conformance · v134
v134 · attribution-reporting-feature-remove-aggregatable-report-limit-when-trigger-cont — conformance probe
5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
server-route-non-empty-context-uncaps |
A trigger registration with a non-empty trigger_context_id is accepted without the 20-report cap. spec ↗ | script | … | |
server-route-empty-context-remains-capped |
An empty trigger_context_id string does not lift the per-source report cap. spec ↗ | script | … | |
server-route-omitted-context-remains-capped |
Omitting trigger_context_id keeps the legacy 20-report cap in force. spec ↗ | script | … | |
server-route-invalid-key-piece-rejected |
A key_piece that is not 0x/0X plus ASCII hex digits is rejected before a response header is emitted. spec ↗ | script | … | |
server-route-header-unsafe-context-rejected |
A trigger_context_id that cannot be emitted safely in the HTTP header is rejected with structured JSON rather than a 500. spec ↗ | script | … |