4 Commits

Author	SHA1	Message	Date
sideshowbarker	5ab804501d	LibWeb: Add “valid floating-point number” for HTMLInputElement.value ... This change adds checking for the following spec requirements: - https://html.spec.whatwg.org/#number-state-(type=number):value-sanitization-algorithm - https://html.spec.whatwg.org/#range-state-(type=range):value-sanitization-algorithm That is, it adds checking that HTMLInputElement.value is what the spec defines as a “valid floating-point number” when the “type” attribute for the HTMLInputElement is either “number” or “range”. This change causes Ladybird to pass all the failing tests at https://wpt.fyi/results/html/semantics/forms/the-input-element/number.html?run_id=5080423051034624 and to match the relevant behavior in Webkit, Blink, and Gecko. Otherwise, without this change, Ladybird fails those tests, and the relevant Ladybird behavior isn’t interoperable with other engines. (cherry picked from commit e76e48421f9ee5e6be12035aee47e91b1656bf0e)	2024-11-04 12:28:33 -05:00
Bastiaan van der Plaat	a2f101c10b	LibWeb: Add input and textarea minlength and maxlength support	2024-03-03 10:02:30 -05:00
Bastiaan van der Plaat	761d824b72	LibWeb: Add basic parse floating point number function	2023-12-04 19:54:43 +00:00
Jonatan Klemets	9812031a02	LibWeb: Implement spec-compliant integer parsing ... We have code inside LibWeb that uses the `AK::StringUtils::convert_to_uint`and `AK::StringUtils::convert_to_int` methods for parsing integers. This works well for the most part, but according to the spec, trailing characters are allowed and should be ignored, but this is not how the `StringUtil` methods are implemented. This patch adds two new methods named `parse_integer` and `parse_non_negative_integer` inside the `Web::HTML` namespace that uses `StringUtils` under the hood but adds a bit more logic to make it spec compliant.	2023-08-24 22:26:53 +01:00