tc39 / tc39/proposal-intl-datetime-alignment
Consider sensitivity to the current time
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
A lot of times, people want to omit the "current" part of a datetime. E.g. show 4 Jan 2026 during 2025 or 2027, but just 4 Jan during 2026. Or 4 Jan 15:17 most of the time, but just 15:17 on 4 Jan itself.
This can, of course, be done with surrounding logic in JavaScript (assuming there aren't cultural aspects of which "current" parts are omitted...), but it can't in HTML or (I think) MessageFormat. If we're aligning JavaScript with those other systems, it might be worth aligning this part too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #2 and compare the requested current-time-sensitive date and time omissions with the HTML and MessageFormat behavior mentioned in the discussion. Determine the proposal scope and expected JavaScript behavior, including cultural considerations; done means the behavior and alignment decision are clearly specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100