Skip to content
This repository has been archived by the owner on May 5, 2022. It is now read-only.

Conflicting Link and <link> #135

Closed
karlcow opened this issue Feb 6, 2019 · 4 comments
Closed

Conflicting Link and <link> #135

karlcow opened this issue Feb 6, 2019 · 4 comments

Comments

@karlcow
Copy link
Member

karlcow commented Feb 6, 2019

What is supposed to happen when at the HTTP level, we have

Link: </css/shiny.css>; as=style; rel=preload

and the HTML document has:

<link href="/css/shiny.css" type="text/css" rel="stylesheet">
  • Checking RFC8288 which obsoleted RFC5988, not clarifying the processing order.
  • And HTML is not clear either about possible conflicts.
  • yoohoo there is another spec talking about it CSSOM but still no clues.
@domfarolino
Copy link
Member

whatwg/html#4224 discusses making it clear (in the HTML Standard) that the semantics of Link: and <link> are the same, so assuming that pans out, I think ultimately having both:

Link: </css/shiny.css>; as=style; rel=preload
<link href="/css/shiny.css" type="text/css" rel="stylesheet">

...per spec, someday, will be the same "conflict" as:

<link href="/css/shiny.css" type="text/css" rel="stylesheet">
<link href="/css/shiny.css" type="text/css" rel="stylesheet">

...in your document, which I don't think is unspecified.

@karlcow
Copy link
Member Author

karlcow commented Feb 6, 2019

@domfarolino I guess you meant

<link href="/css/shiny.css" as="style" rel="preload">
<link href="/css/shiny.css" type="text/css" rel="stylesheet">

@domfarolino
Copy link
Member

Ah, yeah I kinda botched that. Thanks; point remains.

@yoavweiss
Copy link
Contributor

I agree with @domfarolino's analysis. Closing this as this is not actionable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants