From e973c882e2efdd11e10937b27b2ebe49d8b84eba Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Mon, 14 Jun 2021 11:18:56 +0200 Subject: [PATCH] ++comment --- .../blog/ipv6-link-local-support-in-browsers/contents.lr | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/u/blog/ipv6-link-local-support-in-browsers/contents.lr b/content/u/blog/ipv6-link-local-support-in-browsers/contents.lr index 32f18ba..353d833 100644 --- a/content/u/blog/ipv6-link-local-support-in-browsers/contents.lr +++ b/content/u/blog/ipv6-link-local-support-in-browsers/contents.lr @@ -52,9 +52,13 @@ standards. The current status is: * Firefox says whatwg did not define it * Whatwg says zone id is intentionally omitted and and reference w3.org * 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 +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 The progress of IPv6 link local addresses for Firefox is tracked @@ -83,7 +87,7 @@ Thank you! ## IPv6 link local address support in whatwg 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) that