ladybird/Tests/LibWeb/Text/expected/HTML/HTMLInputElement-valueAsNumber.txt

valueAsNumber getter:
number: 100
range: 100
hidden: NaN
text: NaN
search: NaN
tel: NaN
url: NaN
email: NaN
password: NaN
date: NaN
month: NaN
week: NaN
time: NaN
datetime-local: NaN
color: NaN
checkbox: NaN
radio: NaN
file: NaN
submit: NaN
image: NaN
reset: NaN
button: NaN
valueAsNumber setter:
number did not throw: 100
range did not throw: 100
hidden threw exception: InvalidStateError: valueAsNumber: Invalid input type used
text threw exception: InvalidStateError: valueAsNumber: Invalid input type used
search threw exception: InvalidStateError: valueAsNumber: Invalid input type used
tel threw exception: InvalidStateError: valueAsNumber: Invalid input type used
url threw exception: InvalidStateError: valueAsNumber: Invalid input type used
email threw exception: InvalidStateError: valueAsNumber: Invalid input type used
password threw exception: InvalidStateError: valueAsNumber: Invalid input type used
date did not throw: 0
month did not throw: 100
week did not throw: -259200000
time did not throw: 100
datetime-local did not throw: 100
color threw exception: InvalidStateError: valueAsNumber: Invalid input type used
checkbox threw exception: InvalidStateError: valueAsNumber: Invalid input type used
radio threw exception: InvalidStateError: valueAsNumber: Invalid input type used
file threw exception: InvalidStateError: valueAsNumber: Invalid input type used
submit threw exception: InvalidStateError: valueAsNumber: Invalid input type used
image threw exception: InvalidStateError: valueAsNumber: Invalid input type used
reset threw exception: InvalidStateError: valueAsNumber: Invalid input type used
button threw exception: InvalidStateError: valueAsNumber: Invalid input type used
LibWeb+WebContent: Do not include DOM HTML in text test expectations For example, in the following abbreviated test HTML: <span>some text</span> <script>println("whf")</script> We would have to craft the expectation file to include the "some text" segment, usually with some leading whitespace. This is a bit annoying, and makes it difficult to manually craft expectation files. So instead of comparing the expectation against the entire DOM inner text, we now send the inner text of just the <pre> element containing the test output when we invoke `internals.signalTextTestIsDone`. 2024-10-02 13:38:10 -03:00			`valueAsNumber getter:`
LibWeb: Make input type state change handling specification compliant This change ensures that the value sanitization algorithm is run and the text cursor is set to the correct position when the type attribute of an input is changed. 2024-09-10 05:24:00 -03:00			`number: 100`
			`range: 100`
LibWeb: Add test for valueAsNumber 2023-11-13 21:13:50 -03:00			`hidden: NaN`
			`text: NaN`
			`search: NaN`
			`tel: NaN`
			`url: NaN`
			`email: NaN`
			`password: NaN`
			`date: NaN`
			`month: NaN`
			`week: NaN`
			`time: NaN`
			`datetime-local: NaN`
			`color: NaN`
			`checkbox: NaN`
			`radio: NaN`
			`file: NaN`
			`submit: NaN`
			`image: NaN`
			`reset: NaN`
			`button: NaN`
			`valueAsNumber setter:`
LibWeb: Make input type state change handling specification compliant This change ensures that the value sanitization algorithm is run and the text cursor is set to the correct position when the type attribute of an input is changed. 2024-09-10 05:24:00 -03:00			`number did not throw: 100`
			`range did not throw: 100`
LibWeb: Add test for valueAsNumber 2023-11-13 21:13:50 -03:00			`hidden threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`text threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`search threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`tel threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`url threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`email threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`password threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
LibWeb/HTML: Implement valueAsNumber for 'date' input type 2025-02-23 07:34:06 -03:00			`date did not throw: 0`
LibWeb/HTML: Implement <input> element valueAsNumber for 'month' 2025-02-06 22:27:21 -03:00			`month did not throw: 100`
AK/Time+LibWeb/HTML: Fix ISO8601 week conversions This reimplements conversions between unix date times and ISO8601 weeks. The new algorithms also do not use loops, so they should be faster. 2025-08-11 04:07:27 -03:00			`week did not throw: -259200000`
LibWeb/HTML: Correctly convert number to time/local datetime string This fixes a bug where non-zero milliseconds were previously not included if the second component was zero. 2025-08-11 03:03:32 -03:00			`time did not throw: 100`
			`datetime-local did not throw: 100`
LibWeb: Add test for valueAsNumber 2023-11-13 21:13:50 -03:00			`color threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`checkbox threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`radio threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`file threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`submit threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`image threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
			`reset threw exception: InvalidStateError: valueAsNumber: Invalid input type used`
LibWeb: Bring CSS `line-height` closer to other engines This patch makes a few changes to the way we calculate line-height: - `line-height: normal` is now resolved using metrics from the used font (specifically, round(A + D + lineGap)). - `line-height: calc(...)` is now resolved at style compute time. - `line-height` values are now absolutized at style compute time. As a consequence of the above, we no longer need to walk the DOM ancestor chain looking for line-heights during style computation. Instead, values are inherited, resolved and absolutized locally. This is not only much faster, but also makes our line-height metrics match those of other engines like Gecko and Blink. 2024-01-12 08:39:40 -03:00			`button threw exception: InvalidStateError: valueAsNumber: Invalid input type used`