https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • h
    yeah
  • h
    I guess there's a world where you swap the tag, strip the styling down to make them look the same in all cases and then try to have the component make a call which to use
  • g
    yes
  • h
    if it's a post, always use a button
  • h
    well
  • g
    if it's not a link, use a button
  • h
    that's tricky - they'll always both have a link
  • h
    you could have different arguments I guess for link vs submit target
  • g
    where a link is an element that navigates to a predetermined page
  • h
    but that starts pushing more complexity to the user which the whole point of this is to reduce
  • g
    {% buttonlike tag="a", get="/url" %}
    {% buttonlike tag="button", get="/url/a" %}
    {% buttonlike tag="button", post="/url" %}
  • h
    I'd abstract that more and have a curry link/button that calls button with the right argument
  • h
    but then why bother with the buttonlike at all
  • h
    just make the link version and the button version and let them be different
  • h
    which is what I do now
  • g
    yeah
  • g
    have a class that strips all styles and makes links and buttons look the same
  • h
    that's honestly the most common error I see in this situation
  • h
    the dev doesn't style them the same
  • h
    some subtle difference liked a fixed height vs a line height
  • h
    I'm not convinced it's a bad idea to combine the two
  • g
    all: inherit;
  • g
    might be too aggressive idk
  • g
    but you need to override font size etc. anyway
  • h
    a little bit of hyperscript/alpine to handle space and the role element I think handles most of the complaints
  • h
    yeah that approach would work too, preseed the template with styling guarneteed to make the two cases look the same
  • h
    link and button are simple/fundamental enough building from scratch is for the best imho
  • m
    we should spend some time thinking about this: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/206
  • n
    it would be nice if you could use a css selector to indicate which parts of the document you want
  • b
    My unrequested two cents: Using role when there is a default semantic alternative is an undesirable choice. It seems like you are trading complexity in CSS for complexity in JavaScript. I would always choose CSS for longevity. Despite JS feeling simpler because programming, you will see CSS errors. You won't see the JS issues with accessibility without actual accessibility testing.
1...761762763...1146Latest