Laurenz

I would not classify the breaking of a workaround as a regression/urgent. If someone comes up with a solution until the release candidate I'd be happy, but otherwise I'd say...

Resolved by https://github.com/typst/typst/pull/4803

> To be clear, I'm not affiliated with typst Affiliated or not, you're doing a lot for the project and we're very thankful! :)

> Should we make enum and list's width 100% by default? Then you can't have a list in an automatically sized block anymore.

That would break lists in automatically sized containers.

The top one. Sorry I was on my phone and too lazy to quote.

I think that wouldn't be a great UX as you couldn't easily adjust the `width` parameter from list syntax. The issue can be fixed just with changes to the internals...

I had somewhat different plans in this direction. Rather than a data loading function that returns arrays and dictionaries, I was imagining a `html.elem.parse` constructor (or `html.parse` function, not sure...

I think a parser that takes a string and turns it into HTML element content is generally quite useful and should definitely exist. Using this and converting yourself would be...

I think there's no need to support a slot API in `html.parse`. A slot-based templating could also be supported by `html.parse` returning content + a show rule on `html.elem.where(tag: "slot")`....