00:31
<MikeSmith>
can anybody remind me what’s the Bikeshed syntax for referencing a term from a different spec?
00:31
<MikeSmith>
TabAtkins: 🦉 ?
00:32
<TabAtkins>
You just link it like a local term
00:33
<MikeSmith>
TabAtkins: OK see https://github.com/w3c/ServiceWorker/blob/master/docs/index.bs#L2277
00:34
<MikeSmith>
[=service-workers mode=]
00:34
<MikeSmith>
that is meant to point to https://fetch.spec.whatwg.org/#request-service-workers-mode
00:34
<MikeSmith>
but it fails to resolve because I guess some hook is missing from the SW spec source
00:35
<MikeSmith>
$ bikeshed spec
00:35
<MikeSmith>
LINK ERROR: No 'dfn' refs found for 'service-workers mode'.
00:35
<MikeSmith>
<a data-link-type="dfn" data-lt="service-workers mode">service-workers mode</a>
00:36
<TabAtkins>
You running this locally or thru the API?
00:38
<MikeSmith>
locally
00:38
<TabAtkins>
Run `bikeshed update`, make sure your dfn database is up to date.
01:08
<MikeSmith>
TabAtkins: oofs yeah I remember now the Bikeshed docs say to do that
01:13
<MikeSmith>
TabAtkins: thanks, no more errors ⛄️
01:55
<TabAtkins>
MikeSmith: You can also run `bikeshed refs` to search the refs database, to make sure the term exists and has the properties you assume it has.
02:02
<MikeSmith>
TabAtkins: coolーthanks, didn’t know about that one
02:15
<TabAtkins>
that's only your local refs, mind. lets you know if you need to update. ^_^
02:32
<MikeSmith>
TabAtkins: ok
02:34
<MikeSmith>
so the Service Workers spec defines requirements for how UAs must process the value of the Link header for the “serviceworker” link type but it doesn’t actually define what syntax a serviceworker Link header is expected to conform to
02:34
<MikeSmith>
https://w3c.github.io/ServiceWorker/#link-header-processing
02:35
<MikeSmith>
so I am now wondering, Do we have other specs that define the syntax of the value of the Link header for some particular link type?
02:35
<MikeSmith>
HTML doesn’t have any
02:36
<MikeSmith>
and I know there are things like the WebAppSec specs that define new headers, like Referrer-Policy
02:37
<MikeSmith>
but this case is about defining the specific syntax of the value of an existing header
02:40
MikeSmith
looks through https://www.iana.org/assignments/link-relations/link-relations.xhtml
02:45
<MikeSmith>
no luck
03:11
<felixjet>
can i represent elapsed number of days with <time> tag?
03:11
<felixjet>
<time>6</time>, or even <time>Day 6</time>
04:22
<annevk>
felixjet: no, it represents time, not duration
04:23
<annevk>
felixjet: and no relative time either afaik
04:58
<felixjet>
annevk, thanks
15:21
<Lcfvs>
hi here...
15:23
<Lcfvs>
i'm looking about how to make a proposal, please... I would suggest an attribute to indicate a form data is not volatile (which may be usefull for SEO)
15:28
<annevk>
Lcfvs: https://wiki.whatwg.org/wiki/FAQ#Is_there_a_process_for_adding_new_features_to_a_specification.3F
15:28
<annevk>
Lcfvs: once you feel like you've met the bar outlined there, https://github.com/whatwg/html/issues/new would be next
15:28
<Lcfvs>
@annevk thanks :)
21:06
<dmarr>
im trying to figure out the etag/if-none-match dance, when using a proxy layer. i have a GET request to requestb.in using fetch() from my spa - it seemed to get an ETAG at one point, but now i don't see it returned. anyone know how to diagnose that?
21:19
<dmarr>
my sledgehammer approach to avoid stale content in the requests to /api.x was to use cache-control: no-cache in the fetch headers. i wasn't sure how to get the if-none-match header set dynamically