This commit (July 17th, 2018) introduced a new behaviour to Matrix, where the first text input receives keyboard focus when a new block is created.
Since Date fields also have the .text classname, this causes the first Date field's datepicker to automatically toggle open when a new block is added, if there aren't any other text inputs preceding the Date field in that block.
This feels like unintended behaviour.
Seems like it鈥檚 still expected behavior to me? If that鈥檚 the first field, it鈥檚 probably the first thing that authors will want to enter when creating a new block.
The problem with auto-focusing the date field in particular, is that the open datepicker tends to overlap other fields, obscuring context. Feels like a bug to me.
In general, I think Craft is making a few assumptions with the auto-focusing behaviour that I'm not convinced it should make, such as
a) the user never needs to survey the complete FLD for context (e.g., without fields being obscured by an open datepicker)
b) the user will always want to start editing content as soon as the block is created
c) the content model is linear and it'll always make sense for the user to start editing the first (top) field first
I do see where autofocusing is useful for certain workflows, I'm just not convinced it makes sense to have this behaviour as a default for everything (and especially not in regards to date fields). In any case, it would be really cool to have some way of tailoring the auto-focus behaviour in the future :)
Most helpful comment
The problem with auto-focusing the date field in particular, is that the open datepicker tends to overlap other fields, obscuring context. Feels like a bug to me.
In general, I think Craft is making a few assumptions with the auto-focusing behaviour that I'm not convinced it should make, such as
a) the user never needs to survey the complete FLD for context (e.g., without fields being obscured by an open datepicker)
b) the user will always want to start editing content as soon as the block is created
c) the content model is linear and it'll always make sense for the user to start editing the first (top) field first
I do see where autofocusing is useful for certain workflows, I'm just not convinced it makes sense to have this behaviour as a default for everything (and especially not in regards to date fields). In any case, it would be really cool to have some way of tailoring the auto-focus behaviour in the future :)