Bug 29235
Summary: | Fix up user-input value of input[type=url] | ||
---|---|---|---|
Product: | WebKit | Reporter: | Kent Tamura <tkent> |
Component: | Forms | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | ahmad.saleem792, annevk, arv, cmarcelo, darin, ian, jonlee, me, mikey.j.clarke, pkasting, ravi.kasibhatla, syoichi, webmaster |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.whatwg.org/specs/web-apps/current-work/#url-state | ||
Bug Depends on: | 27456 | ||
Bug Blocks: | 19264 |
Kent Tamura
We had better provide some fixing up for values of <input>.
e.g.
If a user specify "www.apple.com" for <input type=url>, a browser fixes it to "http://www.apple.com"
See the discussion in https://bugs.webkit.org/show_bug.cgi?id=27456
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Kent Tamura
*** Bug 53187 has been marked as a duplicate of this bug. ***
Evan Carroll
I'd love to see this fixed. HTML5 websites are being created right now with fields erroneously marked type="text". We could get the desired effect and start building apps now if this bug was closed -- and in the future, UI improvements that pulled from bookmarks, or history could be enjoyed.
Ravi Phaneendra Kasibhatla
As per discussion in https://bugs.webkit.org/show_bug.cgi?id=27456#c25, there were 4 approaches for solving the issue. What is the consensus on the approaches? I am planning to take up this issue and provide the patch for the same.
Kent Tamura
(In reply to comment #3)
> As per discussion in https://bugs.webkit.org/show_bug.cgi?id=27456#c25, there were 4 approaches for solving the issue. What is the consensus on the approaches? I am planning to take up this issue and provide the patch for the same.
Now we can have different strings in HTMLInputElement::value (HTMLInputElement::m_valueIfDirty or value= attribute value) and UI value (innerTextValue, visibleValue()). We can add fix-up implementation to URLInputType::convertFromVisibleValue().
Kent Tamura
*** Bug 99764 has been marked as a duplicate of this bug. ***