Mobile and touch devices will load a different keyboard depending on the inputmode. This is already implemented for several fields eg url and email
This PR enables it for search fields
As search fields are not a separate field type but type="text" we either have to create a new field type or it has to be added via the form xml. Support for the xml option was (surprisingly) already implemented so I just had to add the inputmode=search to the xml.
To test this you will need either a mobile device or a touch enabled computer with a virtual keyboard.
When you enter the search field you will see a slightly different keyboard than normal - the actual layout of which is dependent on your device. On my touch screen it looks like this
In #26797 I created a global string for "Name ascending" and "Name descending"
This PR uses that global string instead of duplicating the string in each component
* [4.0] [a11y] Table Options
The table options drop down contains multiple select inputs
None of them are accessible as they don't have a label
This PR adds a label for each select with a class of sr-only (screenreader only)
Unfortunately there is no label attribute present in the xml son I had to add it. To avoid creating more work for translators I am reusing (where possible) the language string we are using for the default empty value eg Select Position
For test purposes I have only updated administrator/index.php?option=com_modules
If this is ok I will do the same for all filter_XXXX.xml
* JGLOBAL_LIST_LIMIT - add and standardise
* JGLOBAL_SORT_BY
* filter
* cs
* Update filter_tags.xml
* Update filter_associations.xml
* missed one
* conflict fix
* remove unused strings - thanks @quy
* Update filter_featured.xml
* remove unused
* [4.0] com_banners remove popover
This is a proof of concept for #17044 to remove the redundant popovers.
PURELY for the purpose of testing this concept I have quickly displayed the remaining popover as inline text - THIS PART IS NOT FOR REVIEW - it is just to demonstrate how few remaining descriptions we will have
In addition you will notice that the remainining descriptions are not very good. They are manuals not tips, hints or descritpions and can be drastically reduced or rewritten. AGAIN this text is not for review here
* demonstration only
* add com_content config options
* contact item
* one more
* missed one
* added com_users
* menus
* finish com_menus
* com_joomlaupdate
* com_messages
* com_messages
* com_newsfeeds
* com_redirects
* com_search
* com_finder
* com_tags
* com_templates
* com_templates
* com_plugins
* modules first pass
* com_content, com_categories and various
* user profile
* profile again
* com_admin, com_config
* cleanup
* com_fields, com_languages
* user plugins
* plugins two factor
* plugins system
* plugins search
* plugins - authentication
* plugins - captcha
* plugins - content
* plugins - editors
* plugins fields
* oops forgot some modules
* front end views and menu options
* further review
* mod _related
* further remove
* pagination results to pagination summary
* tabs
* language stemmer
* undo
* show rss link
* oops i forgot the tags component
* missed some
* com-config tidyup
* unused banners strings
* unused strings
* frontend edit profile
* mod_feed
* mod articles latest
* modules
* more module stuff
* Labels and descriptions are not used in filters
* review again
* complete module review
* plugin review
* oops i forgot to save this file before committing
