I upgraded to Windows 10 whenever MS offered the free update. I have the autocorrect features turned on in the Typing config section as recommended.
However, even though this is on, this does nothing in IE 11 even though it is mentioned it will in this article on Microsoft Answers (says see Section D).
Is there a trick to get this working? Is there some HTML 5 attribute that also needs to be included for this to work in IE 11 (can't use edge). Spell check works in Chrome and Firefox (only via right-click menu option), so it seems it's an IE 11 issue?
have you tried the spellcheck attribute: https://www.w3schools.com/tags/att_global_spellcheck.asp
<input spellcheck="true">
I am a newbie when it comes to the web development. I am creating a form and in the input tag I added the required attribute. It works on every browser except for safari5. After doing some research I found that the required attribute is not supported by Safari 5. Any suggestions as to what I should do?
As you can see here, form validation isn't fully supported in Safari, IE9 and earlier, and some mobile browsers. You will need to look into a fallback solution for those situations. These fallbacks are typically called polyfills.
HTML5 Please has some recommended polyfills for form validation: http://html5please.com/#form%20validation
One final thing to remember, even if you do client side validation, always do server side validation as well because you should never blindly trust data coming from the user.
I have decided not to support older browsers (IE6 & Before) and alternatively providing a page that forces the user to upgrade their browser. The demographic I am targeting are generally technologically savvy and very few users will encounter this page. What I am hoping to do is not support any browsers older than 5 - 6 years. What would be the best way about to achieve this? Would it be better to ONLY eliminate IE6 and below? What about early versions of Firefox, etc.?
You can read the browser version from the User-Agent string passed by the browser. You want to do a RegEx match on it. Depending on how harsh you want to be you could put a big banner at the top of the page with what you have detected their browser to be and a link for them to upgrade.
You should be able to find libraries in your chosen server-side language to do the parsing for you, save the hard work. An ultra-quick Google returned: https://github.com/tobie/ua-parser
What are important considerations if ditching JavaScript fallbacks?
For cases where HTML5 form validation is used for simple, 3-field contact forms:
Name
Email
Message
Also assuming that HTML5 validation is coupled with good back-end validation (e.g. PHP) to prevent security threats.
While a fallback is still being suggested as good-practice from a code point of view, this has UX considerations as well because from all the modern ones, only mobile browsers lack support for HTML5 form validation — it will depend on the purpose of the contact form and website, but it may or may not be a problem if certain fields go unvalidated.
You should not drop Javascript fallbacks for form validation yet.
IE10 as a stable version is only available on Windows 8. It's still in beta state for windows 7 (and it's still not decided if MS will ever roll it out as an automatic update for 7) and will most likely never be available on Vista and XP which still have considerable market share. So Internet Explorer 8 and 9 are unlikely to disappear so soon.
Also, don't underestimate the mobile market. iPads and Android-based tablets are still gaining importance.
I've just been given a requirement to prevent browsers from saving data entered into specific form fields. It's been years since I've done web dev, and this is a relatively new capability. I was able to find the form field property autocomplete="off", but I can't seem to find any documentation indicating which browsers support it. Can anyone point me in the right direction of a chart of form attributes and browser compatibility?
Be aware that all major browsers are moving towards ignoring the attribute for password fields.
I can only offer anecdotal evidence, but I've yet to come across a browser that fails to respect autocomplete="off", this experience covers:
Firefox 1.5+ (Windows and Ubuntu)
Opera 6+ (Windows and Ubuntu)
Chrome v2+ (Windows and Ubuntu)
Epiphany 0.8 (ish) (Ubuntu)
Midori (I can't remember which version)
Safari v1+ (Windows)
IE 4 - 8, Windows.
I'm aware that Greasemonkey scripts, and presumably other user-scripts, can disable the autocomplete setting.
There's a couple of articles I found that might be useful to you:
How to turn off form auto-completion
Using auto-complete in html forms
Password managers now ignore the autocomplete attribute for password fields in the major browsers as of:
IE11
Firefox 30
Chrome 34
Safari seems to have an opt-in option to ignore them
It should still work fine for disabling autocomplete on form fields, but no longer affects the password manager.
As of Chrome v34, autocomplete="off" is now ignored by default.
This somewhat debatable feature can be disabled in the flags configuration by visiting chrome://flags
http://news.softpedia.com/news/Chrome-34-Seeks-to-Save-All-Your-Passwords-436693.shtml
If you're able to use JavaScript and jQuery, you can place this on load of the html:
$('#theform input').val('');
Except for Maxthon Browser I think, they are famous in china and making a name now worldwide. They don't treat Autotocomplete=off power very well. It won't work with them.
Some solution is not working in modern browsers.
Another solution link is given here. which works in all modern browsers.
Input type=password, don't let browser remember the password
You can use autocomplete="off" in this given soluton
Matter of fact, both username and password fields doesn't react to AutoComplete=off in all the latest browsers.
td;dr: To check on compatibility across browsers, here is an official MDN doc on turning off autocompletion with the link for compatibility - https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion
A little longer answer: Your issue is because of Chrome's autofill feature, and here is Chrome's stance on it in this bug link - https://bugs.chromium.org/p/chromium/issues/detail?id=468153#c164
To put it simply, there are two cases -
[CASE 1]: Your input type is something other than password. In this case, the solution is simple, and has three steps.
Add name attribute to input
name should not start with a value like email or username, otherwise Chrome still ends up showing the dropdown. For example, name="emailToDelete" shows the dropdown, but name="to-delete-email" doesn't. Same applies for autocomplete attribute.
Add autocomplete attribute, and add a value which is meaningful for you, like new-field-name
It will look like this, and you won't see the autofill (and the value you enter won't be cached) for this input again for the rest of your life -
<input type="text/number/something-other-than-password" name="x-field-1" autocomplete="new-field-1" />
[CASE 2]: input type is password
Well, in this case, irrespective of your trials, Chrome will show you the dropdown to manage passwords / use an already existing password and show the prompt to update the cached password. Firefox will also do something similar, and same will be the case with all other major browsers. Have a look at the MDN doc link I shared at the very top.
In this case, if you really want to stop the user from seeing the dropdown to manage passwords or the prompt to save the credentials, you will have to play around with JS to switch input type, as mentioned in the other related questions.