On Thu, Jul 4, 2013 at 5:17 PM, Kyle Huey <m...@kylehuey.com> wrote: > Presumably we could have a blacklist of the handful of protocols that are > internal to browsers and have compat issues. "It violates the standard" > isn't a very compelling argument when the standard is in the process of > being written and nobody implements it.
Then we might as well define them. It's not like their parsing behavior is particularly hard. And this does not just affect new URL(), it affects how e.g. <a> behaves as well. And a large part of the reason of defining this is because of the current mess of nobody following the IETF standards (which were not compatible, URL standard hopefully is)... In any event, this issue seems relatively minor compared to what's involved in getting Gecko to switch URL parsers. -- http://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
