(more info about the types here)。问题是 Chrome 想为我提供超级有用的帮助并验证这些元素,只是它很烂。如果它未能通过内置验证,则除了元素获得焦点之外没有任何消息或指示。我使用 "http://" 预填充 URL 元素,因此我自己的自定义验证只是将这些值......" /> (more info about the types here)。问题是 Chrome 想为我提供超级有用的帮助并验证这些元素,只是它很烂。如果它未能通过内置验证,则除了元素获得焦点之外没有任何消息或指示。我使用 "http://" 预填充 URL 元素,因此我自己的自定义验证只是将这些值......"> (more info about the types here)。问题是 Chrome 想为我提供超级有用的帮助并验证这些元素,只是它很烂。如果它未能通过内置验证,则除了元素获得焦点之外没有任何消息或指示。我使用 "http://" 预填充 URL 元素,因此我自己的自定义验证只是将这些值......" />
In my forms, I'd like to use the new HTML5 form types, for example <input type="url" />
(more info about the types here).
The problem is that Chrome wants to be super helpful and validate these elements for me, except that it sucks at it. If it fails the built-in validation, there's no message or indication other than the element getting focus. I prefill URL elements with "http://"
, and so my own custom validation just treats those values as empty strings, however Chrome rejects that. If I could change its validation rules, that would work too.
I know I could just revert back to using type="text"
but I want the nice enhancements using these new types offers (eg: it automatically switches to a custom keyboard layout on mobile devices):
https://i.stack.imgur.com/uiPln.png
So, is there a way to switch off or customise the automatic validation?
inputmode
attribute, which - if I'm understanding what I read correctly - can be used for specifying what keyboard type should be offered to the user when they interact with the field, without also implying any validation rules. At some point in the future, using the inputmode
attribute instead of the type
attribute will probably be the correct solution to this problem - but not yet.
$('[inputmode]').each(function () { this.attr({type: this.attr('inputmode'), novalidate: true}) });
inputmode
would. Doing things your way, you still can't (for example) read non-numeric values that the user types into an input box of type number
. For example, try typing something non-numeric into the text box in this fiddle and clicking the button.
<input type='number'>
doesn't accept non-numeric values at all?
If you want to disable client side validation for a form in HTML5 add a novalidate attribute to the form element. Ex:
<form method="post" action="/foo" novalidate>...</form>
See https://www.w3.org/TR/html5/sec-forms.html#element-attrdef-form-novalidate
I had a read of the spec and did some testing in Chrome, and if you catch the "invalid" event and return false that seems to allow form submission.
I am using jquery, with this HTML.
// suppress "invalid" events on URL inputs $('input[type="url"]').bind('invalid', function() { alert('invalid'); return false; }); document.forms[0].onsubmit = function () { alert('form submitted'); };
I haven't tested this in any other browsers.
invalid
event and returning false doesn't let the form submit.
I just wanted to add that using the novalidate attribute in your form will only prevent the browser from sending the form. The browser still evaluates the data and adds the :valid and :invalid pseudo classes.
I found this out because the valid and invalid pseudo classes are part of the HTML5 boilerplate stylesheet which I have been using. I just removed the entries in the CSS file that related to the pseudo classes. If anyone finds another solution please let me know.
<form action="" method="" class="" id="" novalidate>
;)
The best solution is to use a text input and add the attribute inputmode="url" to provide the URL keyboard facilities. The HTML5 specification was thought for this purpose. If you keep type="url" you get the syntax validation which is not useful in every case (it is better to check if it returns a 404 error instead of the syntax which is quite permissive and is not of a great help).
You also have the possibility to override the default pattern with the attribute pattern="https?://.+" for example to be more permissive.
Putting the novalidate attribute to the form is not the right answer to the asked question because it removes validation for all the fields in the form and you may want to keep validation for email fields for example.
Using jQuery to disable validation is also a bad solution because it should absolutely work without JavaScript.
In my case, I put a select element with 2 options (http:// or https://) before the URL input because I just need websites (and no ftp:// or other things). This way I avoid typing this weird prefix (the biggest regret of Tim Berners-Lee and maybe the main source of URL syntax errors) and I use a simple text input with inputmode="url" with placeholders (without HTTP). I use jQuery and server side script to validate the real existence of the web site (no 404) and to remove the HTTP prefix if inserted (I avoid to use a pattern like pattern="^((?http).)*$" to prevent putting the prefix because I think it is better to be more permissive)
Instead of trying to do an end run around the browser's validation, you could put the http://
in as placeholder text. This is from the very page you linked:
Placeholder Text The first improvement HTML5 brings to web forms is the ability to set placeholder text in an input field. Placeholder text is displayed inside the input field as long as the field is empty and not focused. As soon as you click on (or tab to) the input field, the placeholder text disappears. You’ve probably seen placeholder text before. For example, Mozilla Firefox 3.5 now includes placeholder text in the location bar that reads “Search Bookmarks and History”: When you click on (or tab to) the location bar, the placeholder text disappears: Ironically, Firefox 3.5 does not support adding placeholder text to your own web forms. C’est la vie. Placeholder Support IE FIREFOX SAFARI CHROME OPERA IPHONE ANDROID · 3.7+ 4.0+ 4.0+ · · · Here’s how you can include placeholder text in your own web forms:
Browsers that don’t support the placeholder attribute will simply ignore it. No harm, no foul. See whether your browser supports placeholder text.It wouldn't be exactly the same since it wouldn't provide that "starting point" for the user, but it's halfway there at least.
I found a solution for Chrome with CSS this following selector without bypassing the native verification form which could be very useful.
form input::-webkit-validation-bubble-message,
form select::-webkit-validation-bubble-message,
form textarea::-webkit-validation-bubble-message {
display:none;
}
By this way, you can also customise your message...
I got the solution on this page : http://trac.webkit.org/wiki/Styling%20Form%20Controls
Just use novalidate in your form.
<form name="myForm" role="form" novalidate class="form-horizontal" ng-hide="formMain">
Cheers!!!
you can add some javascript to surpress those obnoxious validation bubbles and add your own validators.
document.addEventListener('invalid', (function(){
return function(e) {
//prevent the browser from showing default error bubble / hint
e.preventDefault();
// optionally fire off some custom validation handler
// myValidation();
};
})(), true);
If you mark a form element as required=""
then novalidate=""
does not help.
A way to circumvent the required
validation is to disable the element.
Here is the function I use to prevent chrome and opera from showing the invalid input dialog even when using novalidate.
window.submittingForm = false;
$('input[novalidate]').bind('invalid', function(e) {
if(!window.submittingForm){
window.submittingForm = true;
$(e.target.form).submit();
setTimeout(function(){window.submittingForm = false;}, 100);
}
e.preventDefault();
return false;
});
In JSX (Javascript, React, Angular, Vue & ...) add noValidate
(camelCase with the uppercase V
) to form:
<form onSubmit={handleSubmit(data)} noValidate>
As Jakob S said, in pure HTML add novalidate
to form element:
<form method="post" action="/foo" novalidate>...</form>
Success story sharing
novalidate="novalidate"
andnovalidate=""
is valid syntax, too.novalidate="novalidate"
method when you set thenovalidate => true
in the$options
array of theFormHelper::create()
. Thanks bassim for the extra info :)