feat: a shared date and time picker
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- html, rust
- Domain
- accessibility, frontend
Research direction
Read §4.5's native-first rule and the §13.7.5 checklist in the tracking issue #776 before anything else, then confirm the four blockers (Input/text field, Popover, Button, Lucide Icon) have landed. Start with the native <input type="date">/"time"/"datetime-local" path and only add a Popover calendar where native falls short, applying the ARIA date-picker grid pattern, jiff time-zone display and l10n formats. Done means the component plus gallery entry, axe-core and ARIA snapshot rows, a §4.5 contract row, and keyboard-only scenarios passing WCAG 2.2 AA.
Written by the indexing model from the issue text.
Description
Part of #776.
A shared date and time field: native <input type="date">, "time" and "datetime-local" first (§4.5's native-first rule), with a calendar in a Popover only where the native control falls short, the ARIA date-picker grid pattern if built, times shown in the page's time zone through jiff's rules, and every format through l10n.
Needs first: Input and text field, Popover, Button, Icon (Lucide) (see "blocked by").
Acceptance: Meets the bar in the tracking issue: WCAG 2.2 AA in full when it merges, a contract row in §4.5, and every step of §13.7.5 (component, gallery entry, axe-core and ARIA snapshot rows, keyboard-only contract scenarios).
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 56m
- Merged PRs (30d)
- 349
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nledford/Ladderback
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nledford/Ladderback#809 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nledford/Ladderback#759 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nledford/Ladderback#746 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#745 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#647 ·
Maintainers usually reply within 1 day
All issues in nledford/Ladderback
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yantrikos/yantrik-os#1272 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka priority: low tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
macOS 菜单栏托盘图标保留橙色,与系统单色图标风格不一致Possibly taken @xhugoliu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
YizhengWw/HachimoDock#56 · 1 comment ·