input: readonly vs disabled

a readonly element is just not editable, but gets sent when the according form submits. a disabled element isn’t editable and isn’t sent on submit. another difference is that readonly elements can be focused (and getting focused when “tabbing” through a form) while disabled elements can’t.

read more about this in this great article or the definition by w3c. to quote the important part:

Key Differences

1. The Disabled attribute

• Values for disabled form elements are not passed to the processor method. The W3C calls this a successful element.(This works similar to form check boxes that are not checked.)
• Some browsers may override or provide default styling for disabled form elements. (Gray out or emboss text) Internet Explorer 5.5 is particularly nasty about this.
• Disabled form elements do not receive focus.
• Disabled form elements are skipped in tabbing navigation.

2.The Read Only Attribute

• Not all form elements have a readonly attribute. Most notable, the , , and elements do not have readonly attributes (although thy both have disabled attributes)
  Browsers provide no default overridden visual feedback that the form element is read only. (This can be a problem… see below.)
  Form elements with the readonly attribute set will get passed to the form processor.
  Read only form elements can receive the focus
  Read only form elements are included in tabbed navigation.

  Jenkins-CI and Travis-CI

  1. Jenkins-CI Jenkins-CI is a powerful tool for continuous integration: Building/testing software projects continuously. In a nutshell…

  bash color-display grunt script

  bash color-display grunt script Here I wrote a script to restart an node-express server to initialize Angular app. It uses grunt, git, nohup…