my testing IE does treat C| as C: _if_ the scheme is qualified, as in:
file://c|/foo/bar
I know that including the scheme is a slightly different test case than
your original, but in case it's helpful see:
http://web.lookout.net/2011/06/some-browsers-convert-pipe-to-colon-in.html
thanks,
Chris Weber
On 11/24/2012 8:41 PM, Boris Zbarsky wrote:
> A question. What OS or OSes did you test on? Unicode normalization
> differs in some browsers depending on the OS (e.g. different behavior on
> Windows and Mac)...
Thanks for bringing that up Boris, I only tested this on Windows. I'll
try to take a
On 11/24/2012 1:34 AM, Anne van Kesteren wrote:
> This is super awesome. Glad you continued with this. I have a few
> generic points for now:
>
> * No special handling for IPv4. IPv4 should work the same as domain
> names. I.e. the host of http://192/ is 192, not 0.0.0.192.
> * It's still a bit un
On 11/23/2012 10:11 PM, Michael[tm] Smith wrote:
> I wonder if it might make more sense for the URLs being tested for all
> those cases to include a "/" for the pathname. That way they would be
> further isolated to just testing what they're actually intended to test,
> rather that what they're ins
Hello, I've been trying to follow Anne's work with the URL spec, and
working on using the W3C testharness.js for URL testing. I have some
URL testing running, with still more work to do:
http://www.lookout.net/test/url/
The test cases and harness are available at:
https://github.com/cweb/url-te
