Josh Matthews

This is described at https://drafts.csswg.org/resize-observer/#content-rect-h and tested by https://github.com/servo/servo/blob/a6aa21b068e7a9bdd305f4d8fafe881e0e10935c/tests/wpt/tests/resize-observer/notify.html#L195-L233 . Like #40258 this is caused by the [box_area layout query](https://github.com/servo/servo/blob/a6aa21b068e7a9bdd305f4d8fafe881e0e10935c/components/layout/query.rs#L71) being too broad for what this particular code needs.

This is tested by https://github.com/servo/servo/blob/a6aa21b068e7a9bdd305f4d8fafe881e0e10935c/tests/wpt/tests/resize-observer/notify.html#L141-L166 and described in https://drafts.csswg.org/resize-observer/#content-rect-h . We rely on the [box_area layout query](https://github.com/servo/servo/blob/a6aa21b068e7a9bdd305f4d8fafe881e0e10935c/components/script/dom/node.rs#L973) which [applies transforms](https://github.com/servo/servo/blob/a6aa21b068e7a9bdd305f4d8fafe881e0e10935c/components/layout/query.rs#L88-L89); perhaps we can make that a configurable flag?

We were not following the specification for computing the values of the content rect. Additionally, any non-content-box observer would get confused because we never stored the correct size, leading to...

Set Response::cache_state appropriately

2

Relevant spec steps: 1. https://fetch.spec.whatwg.org/#ref-for-concept-response-cache-state%E2%91%A0 2. https://fetch.spec.whatwg.org/#ref-for-concept-response-cache-state%E2%91%A1 3. https://fetch.spec.whatwg.org/#ref-for-concept-response-cache-state%E2%91%A2 We don't appear to implement the steps related to 1 from that list, so we can ignore that. 2 is https://github.com/servo/servo/blob/b256914f0829d8fc5c3082c02cd5fef252f437ce/components/net/http_loader.rs#L1574-L1575...

This requires exposing a new `cache_details` field in [NetworkEventActor](https://github.com/servo/servo/blob/b256914f0829d8fc5c3082c02cd5fef252f437ce/components/devtools/actors/network_event.rs#L29), and making it available as a resource update like https://github.com/servo/servo/blob/b256914f0829d8fc5c3082c02cd5fef252f437ce/components/devtools/actors/network_event.rs#L663 with the string `cacheDetailsAvailable`. The new field will contain two new...

Expose security information for network monitor requests

3

https://github.com/servo/servo/blob/53a2e61fecd42d4d35b7ff5479095cf86e12c1ae/components/devtools/actors/network_event.rs#L320-L326 The values can be "insecure", "weak", "broken", or "secure". Other values that may need to be present with "secure" include: * a `cert` object containing `fingerprint`, `issuer`, `subject`, `validity`...

Create unit tests for the image cache

3

This probably makes the most sense to start after #10767 merges, since the current setup is very dependent on initiating network requests from the image cache.

We don't implement step 5 of https://html.spec.whatwg.org/multipage/webappapis.html#perform-a-microtask-checkpoint https://w3c.github.io/IndexedDB/#cleanup-indexed-database-transactions https://github.com/servo/servo/blob/f4dd2960b89bcc6bae3f9dae5be8964c64c1c2c7/components/script/microtask.rs#L162 This should fix #38772 and #38808 when implemented.

Implement test_driver support

1

We want to support the automated WebBluetooth tests which require [testdriver.js](https://web-platform-tests.org/writing-tests/testdriver.html). This requires building on the work in #22411 and #22420 and following the pattern in https://web-platform-tests.org/writing-tests/testdriver-tutorial.html to add backend...

Stylesheet with no content-type header is ignored

8

Both Firefox and Chrome render https://hardfault.life/ with styles from https://hardfault.life/public/styles.css applied, even though there's no Content-Type header present in the network response for that stylesheet.