Another way of implementing this could be by making use of the `#set_active_class`
Currently, it's only supporting TRUE / (default) FALSE, but by adding string support with 'page', (string) 'true', 'step', 'location', 'date' and 'time' the correct aria label could set based on the usage
This way the place of implementing is responsible for the context, API change is minimal (even backwards compatible possible) and responsibility at the implementer (where context is the highest)
I could make a work-in-progress patch if this is a preferred route to take
Tested and looks good to me
great find
makertimswis → created an issue.
Checked the MergeRequest!121 from @rhezios
Saw the option and it works for me like i expected.
makertimswis → created an issue.
makertimswis → created an issue.
MakerTimSWIS → changed the visibility of the branch 1.0.x to hidden.
MakerTimSWIS → created an issue.
MakerTimSWIS → created an issue.
MakerTimSWIS → created an issue.