WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
Bug 97415
We should not expect percent-escaped hostname for invalid URLs
https://bugs.webkit.org/show_bug.cgi?id=97415
Summary
We should not expect percent-escaped hostname for invalid URLs
Benjamin Poulain
Reported
2012-09-23 17:04:08 PDT
That's a Chrome behavior, no other browser does that.
Attachments
Patch
(10.38 KB, patch)
2012-09-23 17:46 PDT
,
Benjamin Poulain
no flags
Details
Formatted Diff
Diff
Patch
(14.75 KB, patch)
2012-09-24 14:05 PDT
,
Benjamin Poulain
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Benjamin Poulain
Comment 1
2012-09-23 17:46:40 PDT
Created
attachment 165298
[details]
Patch
WebKit Review Bot
Comment 2
2012-09-23 20:50:20 PDT
Comment on
attachment 165298
[details]
Patch
Attachment 165298
[details]
did not pass chromium-ews (chromium-xvfb): Output:
http://queues.webkit.org/results/13989490
New failing tests: fast/url/ipv4.html
Benjamin Poulain
Comment 3
2012-09-23 21:01:09 PDT
> New failing tests: > fast/url/ipv4.html
Interesting, the other two tests should have also failed. I forgot to update the Chromium results, I'll do that tomorrow.
Adam Barth
Comment 4
2012-09-23 21:41:13 PDT
Comment on
attachment 165298
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=165298&action=review
> LayoutTests/ChangeLog:8 > + The URL layout tests encode some Chromium specific behavior.
Yeah, the "PASS" results on these tests are just set to whatever behavior Chromium has. The idea was to make it easy to see what the differences were between GURL and KURL by just reading off the PASS/FAIL results in the apple-mac port. I think it's fine to convert these tests to have the PASS behavior be what we think the right behavior is, especially when there's a clear choice.
Adam Barth
Comment 5
2012-09-23 21:42:11 PDT
annevk might be interested in these sorts of patches since he's working on the URL spec.
Anne van Kesteren
Comment 6
2012-09-24 01:41:04 PDT
Thanks Adam. My plan was indeed for the URL standard to agree with other browsers here. In particular, if a URL is deemed invalid .href just returns the input string and all other components are their default value (typically empty string).
Benjamin Poulain
Comment 7
2012-09-24 11:38:23 PDT
(In reply to
comment #6
)
> Thanks Adam. My plan was indeed for the URL standard to agree with other browsers here. In particular, if a URL is deemed invalid .href just returns the input string and all other components are their default value (typically empty string).
This is the behavior I want. KURL use to partially parse invalid string like GoogleURL, but I fixed it a few months ago. In my opinion, invalid input should not be modified.
Benjamin Poulain
Comment 8
2012-09-24 14:05:23 PDT
Created
attachment 165445
[details]
Patch
Benjamin Poulain
Comment 9
2012-09-24 19:56:06 PDT
Comment on
attachment 165445
[details]
Patch Clearing flags on attachment: 165445 Committed
r129445
: <
http://trac.webkit.org/changeset/129445
>
Benjamin Poulain
Comment 10
2012-09-24 19:56:09 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug