This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We need a way to test support for various <link rel> features - e.g. prerender, prefetch, preload, preconnect. Related threads: - https://github.com/w3c/preload/issues/7 - https://lists.w3.org/Archives/Public/public-whatwg-archive/2015Apr/0000.html Simon's proposal from the mailing list: > For <link rel>, we could solve the feature-testing problem by normalizing the case for supported keywords but not unsupported keywords, so you can check with .rel or .relList: > > function preloadSupported() { > var link = document.createElement('link'); > link.rel = 'PRELOAD'; > return link.rel == 'preload'; > }
To be clear, based on reading the threads linked to in the description for this bug, the bug is not about testing but is instead about the HTML spec defining a new feature for the platform that would facilitate this kind of testing.
HTML5.1 Bugzilla Bug Triage: Incubation needed This bug constitutes a request for a new feature of HTML. The current guidelines [1], rather than track such requests as bugs or issues, please create a proposal outlining the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG [2]. As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process [3]. [1] https://github.com/w3c/html#contributing-to-this-repository [2] https://www.w3.org/community/wicg/ [3] https://wicg.github.io/admin/intent-to-migrate.html