Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing "href" attribute on <link> should trigger re-downloading hyperlink (bugzilla: 22038) #234

Closed
hayatoito opened this issue Jul 6, 2015 · 1 comment

Comments

@hayatoito
Copy link
Contributor

Title: Changing "href" attribute on should trigger re-downloading hyperlink (bugzilla: 22038)

Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22038


comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22038#c0
Morrita Hajime wrote on 2013-05-15 02:48:51 +0000.

From this thread: http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0635.html

Currently it isn't clear what happens if @href-(this-is-inserted-to-avoid-notification-in-migration) is updated on the import
elements. The spec should (probably informally) mentioned that
it loads new import.


comment: 1
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22038#c1
Dimitri Glazkov wrote on 2013-07-18 21:18:37 +0000.

This should be addressed in HTML spec


comment: 2
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22038#c2
Ian 'Hixie' Hickson wrote on 2013-10-23 22:07:44 +0000.

Actually this should be addressed in whatever spec defines the rel="" attribute's value, whichever that is. That's not currently HTML.

See here for how it's done for rel=stylesheet:

http://www.whatwg.org/specs/web-apps/current-work/#link-type-stylesheet

It's not necessarily the case that you want to do it the same way.

@TakayoshiKochi
Copy link
Member

TakayoshiKochi commented Jul 10, 2017

FYI a Chromium bug was also filed at
https://bugs.chromium.org/p/chromium/issues/detail?id=493832

As HTML Imports spec is no longer actively maintained, closing this.

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

No branches or pull requests

2 participants