- From: Trevor Rowbotham <notifications@github.com>
- Date: Mon, 23 Jan 2023 16:18:10 -0800
- To: whatwg/url <url@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 24 January 2023 00:18:23 UTC
@TRowbotham commented on this pull request. > @@ -1016,10 +1352,11 @@ actually doing that with the editors of this document first. <li><p>If <a>c</a> is a U+002E (.) and <var>numbersSeen</var> is less than 4, then increase <var>pointer</var> by 1. - <li>Otherwise, <a>validation error</a>, return failure. + <li>Otherwise, <a>IPv4-in-IPv6-too-many-parts</a> <a>validation error</a>, return failure. `https://[ffff::12xyz]`[(demo)](https://url-demo.trowbotham.com/?url=aAB0AHQAcABzADoALwAvAFsAZgBmAGYAZgA6ADoAMQAyAHgAeQB6AF0A) reports IPv6-unexpected-delimiter for me, but modifying it slightly to `https://[ffff::12.12xyz]`[(demo)](https://url-demo.trowbotham.com/?url=aAB0AHQAcABzADoALwAvAFsAZgBmAGYAZgA6ADoAMQAyAC4AMQAyAHgAeQB6AF0A) shows the problem as the parser needs to encounter at least one `.` before taking that code path. Your suggestion of using IPv4-in-IPv6-unexpected-code-point seems reasonable to me. I'd be interested to hear other peoples opinions. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/url/pull/502#discussion_r1084702112 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/url/pull/502/review/1266626927@github.com>
Received on Tuesday, 24 January 2023 00:18:23 UTC