You could try using a background-image with a unique url and only display the element when the user clicks on another element. There would be lots of state to manage, but the css can be generated.
This way you can send arbitrary http requests with meaningful payloads without JS.
Web Dev full-stack [LAMP] since 2005, but much heavier on the JS stuff these days.
Jack of all Stacks, Master of some.
Always looking to learn new things. Always glad to help out, just ask.
Location
Atlanta, GA
Education
B.S. in Biochemistry 2004, M.S. in Computer Information Systems 2007
background images don't work in most email clients.
Although your suggestion made me think they could use multiple submit buttons and based on selection a different button would be visible containing the values in the url it submits to. [makes for ugly inaccessible code though, but all email code is fugly]
Yep, no "submit" button. Honestly I haven't figured out that part yet either, hoping to work with one of the devs on my team to figure it out.
You could try using a
background-imagewith a unique url and only display the element when the user clicks on another element. There would be lots of state to manage, but the css can be generated.This way you can send arbitrary http requests with meaningful payloads without JS.
background images don't work in most email clients.
Although your suggestion made me think they could use multiple submit buttons and based on selection a different button would be visible containing the values in the url it submits to. [makes for ugly inaccessible code though, but all email code is fugly]
Ah, such is the wild west of HTML emails! I had no idea background-image wasn't supported, that's pretty crazy.
background-imagehas pretty good support in email, but nothing's ever a given in the world of email development.