-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Align URL Processing rules for SVG #32014
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
EWS run on previous version of this PR (hash b889ece) |
EWS run on previous version of this PR (hash ab1e0b9) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, makes sense. Note there's a typo in the commit message (algin).
https://bugs.webkit.org/show_bug.cgi?id=269522 rdar://problem/123475267 Reviewed by NOBODY (OOPS!). This patch aligns WebKit with Blink / Chrome and Web Specification [1]: [1] https://url.spec.whatwg.org/#url-parsing As per web specification, it is to trim leading and trailing whitespaces for SVG fragment Identifier and IRI. It was discussed in following: [2] w3c/svgwg#781 * Source/WebCore/svg/SVGURIReference.cpp: (SVGURIReference::fragmentIdentifierFromIRIString): (SVGURIReference::targetElementFromIRIString): * LayoutTests/TestExpectations: Add comment for progressed tests
EWS run on current version of this PR (hash 2459f10) |
Done. Thanks for noting down. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't this still do the incorrect thing if you have #foo<tab>bar
or some such? I think the problem is that we're not putting all inputs through the URL parser and maybe recording there whether it was a local URL? That there's no good specification for this doesn't help.
Isn't |
Not if all you do is trim. In particular this neither implements step 1.3 or step 3 of https://url.spec.whatwg.org/#concept-basic-url-parser correctly as far as I can tell, both pertaining to the removal of certain code points within a URL. |
Closing this since if the change is more involved, I wouldn't be right person to tackle it. Commented on bugzilla as well to account for Anne's input. |
@annevk @Ahmad-S792 is there an issue in using WebKit/Source/WTF/wtf/URLParser.cpp Lines 1124 to 1128 in f5f143e
|
2459f10