[#46442] - [7.0][RFC] native date picker [a11y] [i8n]
- New
- Medium
- Build: 5.4-dev
- # 46442
Yes I know I wrote joomla 7 but this would be a big change and I think that would be the first version we could apply it to.
We currently use javascript as a datepicker. It is very difficult to maintain, is not accessible and is missing functionality that people want in a modern app eg start/end limits and we have lots of open bugs https://github.com/joomla/joomla-cms/issues?q=is%3Aissue%20state%3Aopen%20calendar
Historically the reason for using our own datepicker is so that it can support non-gregorian calendars and historically javascript was the only way to create a datepicker.
Today (nov 2025) there are even fewer countries that use a non-gregorian calendar for civil dates.[1]
Today there is no reason to use a javascript datepicker at all for gregorian calendars. We can use the browser native datetime functionality. It is fast, maintenance free, (more) accessible and offers the missing functionality users are requesting
More information and examples at https://pikaday.dbushell.com/
[1] Non-gregorian calendar
Iran, Afghanistan, Ethiopia, Thailand (year counting).
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
| Title |
|
||||||
| Labels |
Added:
RFC
|
||
| Labels |
Removed:
RFC
|
||
| Title |
|
||||||
| Labels |
Added:
RFC
|
||
I actually see it as a bonus that the language of the calendar will always be in my language - what I am not sure of yet is if the ui supports the correct start of the week for that local.
what I am not sure of yet is if the ui supports the correct start of the week for that local.
Should work. And depend from User OS configuration.
I am not a representative of the groups that use the Solar Hijri calendar.
I just wanted to mention regarding
#46442
that there is also this link:
https://babakhani.github.io/PersianWebToolkit/doc/persian-date/
But I don't know what is correct. I only know that fundamental changes and adaptation put a lot of pressure on extension developers.
Therefore, perhaps a gradual change with simultaneous support for the old calendar could be a solution, if it's feasible.
It should be easy.
Can just replace
calendartodatetimefield in all XMLs, or extendCalendarFieldfromDatetimeFieldfield class.However, 2 questions opened: