my only advice if you really want to put html in atproto records is to never assume a specific medium. no inline styles, and probably no classes either. do custom elements instead
Comments
Log in with your Bluesky account to leave a comment
you're working with an (objectively) awful markup format for a decentralized protocol, at least make it easier for you to move away or maintain it in the long run
See HTML Standard, 13.2 Parsing HTML documents. If it's inside a table, the parser expects only a small subset of relevant elements (thead, col, td...). If it encounters anything else, it enables "foster parenting", which causes the element to be inserted after the table
Comments