fix: limit due date input length in SetDueDateDialog (part of #18553)

[vinay-singh-dev]

Purpose / Description

Part of issue #18553 highlights that the "Set due date" dialog in the
Browser allows extremely large values (e.g. 1000000000 days).

This PR addresses the checklist item:

Browser → Set due date → Limit the number

An InputFilter is added to restrict the number of digits that can
be entered in the due date input fields.

Fixes

Addresses part of #18553

Specifically fixes the following item:

Browser → Set due date:

• Limit the number

Approach

Added InputFilter.LengthFilter to the EditText fields in
SetDueDateDialog.kt.

Applied to:

• Single day input
• Range start input
• Range end input

This prevents extremely large values while maintaining
support for large but reasonable intervals.

How Has This Been Tested?

Tested using the debug build on an Android emulator.

Steps:

1. Open a deck.
2. Go to Browser → select a card → Set due date.
3. Enter very large values (e.g. 1000000000).
4. Confirm the input stops accepting digits after the limit.
5. Verify normal values (10, 365, 2000) still work.
6. Confirm due dates update correctly after pressing OK.

Test environment:

• Android Emulator
• Android SDK 34

Learning

Reviewed the dialog implementation in SetDueDateDialog.kt
and how input changes are handled using doOnTextChanged.

Checklist

Please, go through these checks before submitting the PR.

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

Screenshots

[david-allison]

Cheers! Got a screenshot?

• Could you comment a justification for 5 figures:

Anki Default Maximum Interval: 100 years ~= 36,525 days, so 5 digits makes sense

[vinay-singh-dev]

Thanks!

I chose a 5-digit limit because Anki’s default maximum interval is around 100 years (~36,525 days).
Allowing 5 digits ensures that valid intervals up to this range can still be entered while preventing extremely large values like 1000000000 days.

Here is a screenshot showing the input field after applying the limit.

[BinaryBhaskar]

It would be great if you directly added the screenshot to the PR description, also a small suggestion to limit the img-width when uploading it so it isn't so big.

[vinay-singh-dev]

thanks for your suggestion i will keep that in mind

[david-allison]

Could you edit the commit message with a brief justification of the number selected, and could I see what the 'invalid state' looks like?

Does the value go to 99999, or just stop allowing more input?

[vinay-singh-dev]

Thanks for the suggestion.

The commit message has been updated with the justification for the
5-digit limit (~36,525 days ≈ 100 years).

For the invalid state: the input does not convert the value to 99999.
Instead, the InputFilter prevents additional characters from being entered.

For example, if the user types 123456, the field remains 12345
and no further input is accepted.

I've attached a screenshot showing this behaviour.

[david-allison]

Cheers!

[ZornHadNoChoice]

Thanks for contributing!

Applied to:

• Single day input
• Range start input
• Range end input

I just want to let you know that the two range inputs are already limited to 5 digits.