Skip to content

Conversation

@Achal-Aggarwal
Copy link
Contributor

...ields and unit tests.

Other one was #1758

http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=31347

Instructions
Just merge that code branch and use HTML5 attribute.
For attribute

  1. placeholder : use hint=”Placeholder text” to set placeholder
  2. required : use required=”true” or required=”required” or required=”1” to make field required
  3. autocomplete : use autocomplete=”false” or autocomplete=”off” or autocomplete=”0” to disable autocomplete.
  4. autofocus : use autofocus=”true” or autofocus=”on” or autofocus=”1” to set focus automatically to the field.
  5. spellcheck : use spellcheck =”false” or spellcheck =”off” or spellcheck =”0” to disable spellcheck.
  6. multiple : use multiple=”true” or multiple=”required” so that field can accept multiple values of its type.
    There is little bit refactoring with respect to boolean attributes (disabled, readonly), so everything should work as it does previously.

For the non-supported browsers, fallback js is automatically loaded to support it
Usage of some common attributes are on http://docs.joomla.org/Text_form_field_type/3.2

Install this component and test new field attributes.
https://docs.google.com/file/d/0B3rA3UKTXpVsV2ttNUE5MGNqWkU/edit?usp=sharing

Note only attributes work with this component as this PR is for only New Attributes

@Achal-Aggarwal
Copy link
Contributor Author

replacing #1758

@nicksavov
Copy link
Contributor

Hi Achal,

Looks like this is out-of-sync. Could you update it to master?

@Achal-Aggarwal
Copy link
Contributor Author

Sorry for that. It is in sync with master now.

@wilsonge
Copy link
Contributor

I'm not going to envy the person who's going to solve the merge conflicts between field.php in repeatable form elements and this :P

@Achal-Aggarwal
Copy link
Contributor Author

Install this component and test new field attributes.
https://docs.google.com/file/d/0B3rA3UKTXpVsV2ttNUE5MGNqWkU/edit?usp=sharing

Note only attributes work with this component as this PR is for only New Attributes

@Achal-Aggarwal
Copy link
Contributor Author

For both new attributes and types see PR #1842

@Achal-Aggarwal
Copy link
Contributor Author

Closing this one. Now I will maintain only one PR for the whole project i.e. #1842

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants