On Thu, Jul 4, 2013 at 1:45 AM, Anne van Kesteren <[email protected]> wrote:
> On Wed, Jul 3, 2013 at 4:08 PM, Benjamin Smedberg <[email protected]> > wrote: > > I don't understand why it matters. chrome: and resource: are both > > gecko-specific extensions and we have no desire to standardize them. > > Chromium uses a different scheme for their chrome: protocol. > > Because doing so would be a violation of the standard. It's pretty > clear on what the results must be for any given input. Having > differences for some unknown-in-advance schemes would be bad. > > > -- > http://annevankesteren.nl/ > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform > 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. - Kyle _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
