On 3/19/15 3:16 AM, Anne van Kesteren wrote:
That is in our implementation
Yes, because it was a security bug as specified, iirc.
Of course no one else implements searchParams at all, or plans to.
But as long as we're talking implementations, last I checked no one else
even implemented URLUtils on Location. For example, Chrome and Safari
have .username/.password on URL but not on Location.
and still an outstanding issue in the
specification.
Yes...
And the fact that your getters
and most of your setters might suddenly start throwing when you least expect
them to.
Is that defined?
Sure. You have a Location object, the corresponding navigation context
is navigated cross-origin, suddenly most of your accessors (but not all)
are dead in the water.
I don't think so. The various component attributes all return what you'd expect.
Not in implementations; see above.
Also, https://code.google.com/p/chromium/issues/detail?id=436377 was
committed a while back.
Mmm, lovely.
-Boris
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform
