https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    you have to wrap them in table tags to get them to parse appropriately
  • l
    Right. So this is related to reparenting, I think.
  • m
    I don't know about that concept, but it sound relevant
  • l
  • l
    One min... hunting for the right section...
  • m
    \> reading docs
  • m
    NOT ON MY WATCH
  • l
    So, here's what I remember from my foggie decade ago work... stuff like "tr" and "td" are moved around as part of tree construction
  • w
    I was able to write a temporary workaround, now it works I will open a github issue tomorrow, when I have some time after work
  • m
    thank you adam!
  • l
  • l
    its called "foster parenting"
  • l
  • l
    So, yea, that's going to be a .... huge cluster.
  • w
    This feature request may be a solution: https://github.com/bigskysoftware/htmx/issues/44 So I could send a table with the only one row, which I would like to swap oob. And after the table, I could define other oob elements as well
  • m
    we'll figure it out
  • m
    this is the fun stuff
  • b
    I don't mean to keep going on and on about this, but a discussion about Github discussions was had over on the Craft CMS server. Ok, now I'm done.
  • l
    @mysterious-toddler-20573 So, that this is a edge-case ridden challenge isn't a surprise.
  • m
    only solution: write our own HTML parser
  • l
    @User You can "demote" an issue to a discussion thread?
  • m
    how hard can it be?
  • m
    😑
  • l
    See @mbostock's htl for a mini-tokenizer
  • l
    but it can't help you with this foster-parenting nonsense
  • l
    @User if you can demote a poorly-constructed "issue" to a "discussion" that's a huge win.
  • l
    Then you don't piss off the contributor; and you keep the issue list cleaner
  • l
    ie, often times people just want to be heard; they don't often need to correspond to actionable changes
  • l
    (I like to flag things like that as "Documentation" issues...)
  • b
    Possibly, I would likely just relabel it to "question" and close out once it becomes stale (after a response, of course).
1...929394...1146Latest