ungleich-public/ungleich-staticcms
6
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

++comment

Browse source
This commit is contained in:
Nico Schottelius 2021-06-14 11:18:56 +02:00
parent c9bc8d41ee
commit e973c882e2
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
content/u/blog/ipv6-link-local-support-in-browsers/contents.lr
View file

@ -52,9 +52,13 @@ standards. The current status is:
* Firefox says whatwg did not define it * Firefox says whatwg did not define it
* Whatwg says zone id is intentionally omitted and and reference w3.org * Whatwg says zone id is intentionally omitted and and reference w3.org
* w3.org has a longer reasoning, but it basically boils down to * w3.org has a longer reasoning, but it basically boils down to
"Chrome does not do it and it's complicated and nobody needs it" "Firefox and chrome don't do it and it's complicated and nobody needs it"
* Chromium says it seems not to be worth the effort * Chromium says it seems not to be worth the effort
Given that chain of events, if either Firefox, Chrome, W3.org or
Whatwg where to add support for it, it seems likely that the others
would be following.
## IPv6 link local address support in Firefox ## IPv6 link local address support in Firefox
The progress of IPv6 link local addresses for Firefox is tracked The progress of IPv6 link local addresses for Firefox is tracked
@ -83,7 +87,7 @@ Thank you!
## IPv6 link local address support in whatwg ## IPv6 link local address support in whatwg
The situation at [whatwg](https://whatwg.org/) is that there is a The situation at [whatwg](https://whatwg.org/) is that there is a
[closed bugreport on github](https://github.com/whatwg/url/issues/392) [closed bug report on github](https://github.com/whatwg/url/issues/392)
and [in the spec it says](https://url.spec.whatwg.org/#concept-ipv6) and [in the spec it says](https://url.spec.whatwg.org/#concept-ipv6)
that that