Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
The field labels for the daterange field widgets are ambiguous. They simple appears as "Start" and "End".
Proposed resolution
Update the labels to "Start date" and "End date".
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#15 | 2796145-15.patch | 1.01 KB | mpdonadio |
#6 | daterange_field_labels-2796145-6.patch | 1.01 KB | kunalkursija |
#2 | 2796145-02.patch | 1.09 KB | mpdonadio |
Comments
Comment #2
mpdonadioNot sure what else needs to be done here.
Comment #3
hass CreditAttribution: hass commentedThis should better named "Start date" and "End date". I would also translate it this way in German. We may need no context than.
Comment #4
dishabhadra CreditAttribution: dishabhadra at Blisstering Solutions, Iksula commentedComment #5
kunalkursija CreditAttribution: kunalkursija at Iksula, Blisstering Solutions commentedComment #6
kunalkursija CreditAttribution: kunalkursija at Iksula, Blisstering Solutions commentedAdding revised patch.
Comment #7
mpdonadioThe scope of the issue was just to add the translation context, not to change the actual labels (which would not(?) be 8.2.x eligible, not 100% sure if this policy also applies to experimental modules). There are also hidden labels "Date" and "Time" on the Element, so I am not sure if this change really makes sense from a UX/A11Y perspective.
Comment #8
jhedstromAgree that changing the label is out of scope for this issue--feel free to open a new one (which would need UX/A11Y evaluation) for that.
I think #2 is good to go unless there's more to be done? Not sure if translation contexts are testable or not?
Comment #9
hass CreditAttribution: hass commentedContext does not scale on l.d.o. It should not used whenever possible.
Comment #10
jhedstromThis issue was specific to adding a translation context, but the feedback indicates these should not be used. What's the next step here?
Comment #11
mpdonadioPinging @GaborHojtsy for an opinion here.
Comment #12
jhedstromLooks like #11 intended this to be assigned to Gabor.
Comment #13
Gábor HojtsyI personally think changing the string themselves would be preferable. The granularity of a 'Date range field label' context sounds too much to me. I also believe we can change strings in new minor releases (eg. 8.2 to 8.3).
Comment #14
Gábor HojtsyComment #15
mpdonadioThanks Gábor.
This is just the patch in #6. It applies to both 8.2.x and 8.3.x. Since this is an experimental module, I think we can apply it to both, but I bumped up the version to 8.3.x and the committers can decide.
Comment #16
jhedstromThis looks good. IS was already updated as part of #15, so removing that tag.
Comment #18
Gábor HojtsyUnrelated fails in aggregator tests.
Comment #20
Gábor HojtsyHum, now failing on another unrelated CommentHalJsonBasicAuthTest...
Comment #21
alexpottComment #22
alexpottCommitted f3baea1 and pushed to 8.3.x. Thanks!
Comment #24
Gábor HojtsyYay, thanks!