- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Wed, 14 Nov 2012 10:35:57 -0800
- To: WHATWG <whatwg@whatwg.org>
IPv6 Parsing: * Opera does not appear to support IPv4 addresses in the parser, is that intentional? Putting http://[fd::2.2.3.4]/ in <a> gives protocol opera: and pathname illegal-url-... href returns the input. * Chrome supports "IPv4-like" syntax no other browser supports, e.g. http://[::129.144.52]/ (missing fourth IPv4 component). I do not plan on allowing that. IPv6 Model/Serializing: * All browsers lowercase. http://[FFFF::]/ -> http://[ffff::]/ * Chrome normalizes IPv4 away. I kinda a like that, but wonder if it's problematic? http://[fD::2.2.3.4]/ -> http://[fd::202:304]/ * Chrome follows http://tools.ietf.org/html/rfc5952#section-4 but no other browser does. I think it makes sense to follow Chrome here. Chrome's implementation (except for parsing invalid IPv4) makes a lot of sense I think as it allows for minimizing what needs to be stored internally. It only requires a sequence of eight 16-bit components. Feedback appreciated. -- http://annevankesteren.nl/
Received on Wednesday, 14 November 2012 19:01:48 UTC