Gabriel Radanne
Gabriel Radanne
That specification is indeed pretty awkward, but I would prefer to avoid "just using a string". In this case, it seems we could start with a fairly simple model such...
Nice work! Unless we find a good way to encode the property "area is only allowed in map" that does not make typing of other elements more complex, I think...
Oh sure, we need to fix this. The question is how faithful to the spec we make the typing constraints. I will take a look at the spec in details...
@shepard8 Sorry for the very long delay. Could you make a PR with all your changes ?
Yes, it's sort-of-known that `indent:true` is not very good with `pre` elements (see https://github.com/ocsigen/tyxml/issues/285). In the meantime, disable indentation should work well. It's not clear to me how to solve...
That might work, could you try it ?
`type` in script is already supported through the `a_mime_type` attribute (we have do distinguish it from `a_input_type`). I agree we should support web components. Contribution welcome!
Unclosed elements like in your link are improper HTML and only work because of sloppy parsing. In general, you should avoid w3school, it's not a good source, prefer MDN. As...
I see. We should definitely handle that. The smart constructors in the ppx are made in a way that should allow us to handle that, even if it might be...
> can it be achieved by functorizing Lambda Soup over its tree representation somehow? Either that, or expecting a tree walker (see Xml_sigs.Iterable).