05:18
<annevk>
Noam Rosenthal: I double checked; WebKit would object to exposing that information as we think revealing the precise text an end user might be looking at too revealing
08:01
<Noam Rosenthal>
Noam Rosenthal: I double checked; WebKit would object to exposing that information as we think revealing the precise text an end user might be looking at too revealing
Thanks for checking, let me discuss it internally
08:27
<Noam Rosenthal>
annevk: that behavior in navigation timing also exists in Safari
08:28
<Noam Rosenthal>
open https://www.gov.uk/passport-fees#:~:text=Fees%20for%20returning%20supporting%20documents and run performance.getEntries()[0].name
08:34
<annevk>
Ouch, I should have double checked that.
08:35
<annevk>
I guess this is not yet covered by WPT?
08:35
<Noam Rosenthal>
annevk: all good, let's find a way where fixing the privacy issue doesn't create both a backwards compat issue and an interop issue
08:36
<Noam Rosenthal>
annevk: no WPT yet. https://issues.chromium.org/issues/40136467 is the chromium bug
09:10
<sideshowbarker>

annevk: About https://developer.mozilla.org/en-US/docs/Web/API/Request/cache#:~:text=If%20there%20is%20no%20match%2C%20the%20browser%20will%20respond%20with%20a%20504%20Gateway%20timeout%20status.

only-if-cached — The browser looks for a matching request in its HTTP cache.

  • If there is a match, fresh or stale, it will be returned from the cache.
  • If there is no match, the browser will respond with a 504 Gateway timeout status.

Do UAs (any) actually do that? I can’t recall the Fetch spec ever specifying that. Maybe it’s in some other spec?
Did the Fetch spec ever say it should return anything other than a network error?

13:05
<evilpie>
What's happening with https://github.com/whatwg/html/pull/10022 ?
16:20
<annevk>
TabAtkins: are you around? Should <input type=color> essentially require its value to be an "absolute color"?
16:28
<TabAtkins>
I'm not, I'm on a cruise ship right now. Ping Lea or Chris, or wait a week for me