- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
My company updated Chrome a couple of weeks ago. When that update happened, users lost the ability to select the text in form elements if that element was marked as "disabled" in the HTML. (Fields with readonly="readonly" were still selectable.) Since essential fields like ticket numbers, that users routinely copy and paste into emails, became unselectable, this "small" annoyance actually caused quite a stir and some (wrongful) backlash against SNOW.
I have put a global UI Script in place (Geneva Patch 8 hotfix 1):
try{
$j( document ).ready(function() {
$j('input.form-control').removeAttr('disabled');//edited jQuery selector to reflect need to avoid select-type elements
} catch(e) {
if(g_user.hasRole('admin')){
alert(e.message);
}
}
We've just started testing it. I don't see any worrisome performance impacts from a cursory inspection. I could have improved the specificity of the jQuery selector to also look for the disabled class attribute, but I was concerned about performance.
Please let me know if you have any issues with the same.
In the spirit of sharing,
Trey Carroll
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.