ladybird/Tests/LibWeb/Text/input/css/attr-serialization.html

<!DOCTYPE html>
<script src="../include.js"></script>
<script>
    test(() => {
        function serialize(input) {
            document.body.style.content = input;
            println(document.body.style.content);
        }

        serialize('attr(foo)');
        // FIXME: This should produce `attr(foo)` but doesn't yet.
        serialize('attr(    foo    )');
        serialize('attr(foo, "fallback")');
        // FIXME: This should produce `attr(foo, "fallback")` but doesn't yet.
        serialize('attr(   foo   ,    "fallback"   )');
        serialize('attr(foo raw-string)');
        // FIXME: This should produce `attr(foo raw-string)` but doesn't yet.
        serialize('attr(  foo   raw-string  )');
        serialize('attr(foo raw-string, "fallback")');
        // FIXME: This should produce `attr(foo raw-string, "fallback")` but doesn't yet.
        serialize('attr(  foo  raw-string  ,   "fallback"  )');
        serialize('  attr(foo)     attr(bar) attr(baz)  ');
    });
</script>
Meta: Add DOCTYPEs to most text tests 2025-03-18 19:28:35 +01:00			`<!DOCTYPE html>`
LibWeb: Stop adding extra whitespace when serializing CSS Functions Otherwise `attr(\|name, "fallback")` becomes `attr(\| name , "fallback")` The test here is slightly aspirational. There are other rules for serialization we don't follow (like stripping whitespace entirely from many places) so these are marked with FIXMEs. 2023-09-19 20:45:28 +01:00			`<script src="../include.js"></script>`
			`<script>`
			`test(() => {`
			`function serialize(input) {`
			`document.body.style.content = input;`
			`println(document.body.style.content);`
			`}`

			`serialize('attr(foo)');`
			// FIXME: This should produce `attr(foo)` but doesn't yet.
			`serialize('attr( foo )');`
			`serialize('attr(foo, "fallback")');`
			// FIXME: This should produce `attr(foo, "fallback")` but doesn't yet.
			`serialize('attr( foo , "fallback" )');`
LibWeb: Remove now-invalid attr() type support Previously the type argument in attr() could be the name of a CSS type on its own. This has changed, and now only `raw-string` (previously `string`) or the name of a dimension unit is allowed. Other types and more complex grammar use the `type()` function, which we don't yet support. I've updated the syntax comment, but not the algorithm itself, which will be reimplemented in a later commit. 2025-03-03 16:17:41 +00:00			`serialize('attr(foo raw-string)');`
			// FIXME: This should produce `attr(foo raw-string)` but doesn't yet.
			`serialize('attr( foo raw-string )');`
			`serialize('attr(foo raw-string, "fallback")');`
			// FIXME: This should produce `attr(foo raw-string, "fallback")` but doesn't yet.
			`serialize('attr( foo raw-string , "fallback" )');`
LibWeb/CSS: Insert whitespace between tokens in serialized UnresolvedSV Otherwise, `margin: var(--foo) var(--bar)` would be wrongly serialized as `margin: var(--foo)var(--bar)` 2024-10-15 10:21:40 +01:00			`serialize(' attr(foo) attr(bar) attr(baz) ');`
LibWeb: Stop adding extra whitespace when serializing CSS Functions Otherwise `attr(\|name, "fallback")` becomes `attr(\| name , "fallback")` The test here is slightly aspirational. There are other rules for serialization we don't follow (like stripping whitespace entirely from many places) so these are marked with FIXMEs. 2023-09-19 20:45:28 +01:00			`});`
			`</script>`