16.06.2011 11:59, Lachlan Hunt wrote:
On 2011-06-15 17:59, Boris Zbarsky wrote:
On 6/15/11 5:07 AM, Mykyta Yevstifeyev wrote:
The point of this comment is to propose abandoning normalization of
'about' URIs because of some ad hoc behavior of an only application -
Gecko.
No, it's to propose abandoning normalization because it's not
necessarily compatible with existing deployed uses of about:,
Probably. Because of this in my previous messages I proposed abandoning
making the spec. Standards Track.
not
clearly compatible with the web security model,
How?
and because the
normalization is not defined in the spec.
Normalization is defined in RFC 3986.
The Gecko behavior is just an
illustration of the first point.
The purpose of our draft is to give a stable specification of the
scheme
Yes, this is fine.
But see above.
and normalize all existing types of behavior with regard to
handling 'about' URIs. It will be easier for Gecko to change its
behavior rather than for other apps to do this.
Mykyta, we do need to make this spec document reality, particularly
where implementations are unwilling to make changes.
I agree; but different existing behavior makes this impossible. We
can't list everything which is currently supported by all
implementations in the Standards Track document, but we can do this in
the Informational.
Mykyta
If it doesn't do that, then the spec is useless. I will be reviewing
the options and look into exactly how other browsers handle these
cases, and make appropriate changes to the spec.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf