Writing a blog post about the issue with links nested in buttons, and was wondering if ChatGPT would be able to come to the same conclusions as I did:
First time it only "fixed" my quotation marks around the href/click handler (changed them to double quotes).
Then it took the <a> out of the <button> and as a solution moved the <button> inside the <a>.
On third try it told me to go for either an <a> or a <button> but advised me to add an aria-label that's different from the visual label.
💩
Sarah L. Fossheim /
npub17c…sx33s
2025-02-12 16:41:13
Author Public Key
npub17cey7fegq79uu7ljc0hmsc2hv3sedrqr4j0h98a6tysk8vg49xdsdsx33sPublished at
2025-02-12 16:41:13Event JSON
{
"id": "5819a0e0205431022c719c3ca169629936266a96447f545d4e5c6503b3464571",
"pubkey": "f6324f2728078bce7bf2c3efb861576461968c03ac9f729fba592163b115299b",
"created_at": 1739378473,
"kind": 1,
"tags": [
[
"proxy",
"https://front-end.social/users/fossheim/statuses/113991907639757009",
"activitypub"
]
],
"content": "Writing a blog post about the issue with links nested in buttons, and was wondering if ChatGPT would be able to come to the same conclusions as I did:\n\nFirst time it only \"fixed\" my quotation marks around the href/click handler (changed them to double quotes).\n\nThen it took the \u003ca\u003e out of the \u003cbutton\u003e and as a solution moved the \u003cbutton\u003e inside the \u003ca\u003e.\n\nOn third try it told me to go for either an \u003ca\u003e or a \u003cbutton\u003e but advised me to add an aria-label that's different from the visual label.\n\n💩",
"sig": "c8c9027d1233eeff987e5a1a37c7a9c19536915bda1bffc5e4d282db599e41be7e27f467b38ef85a43b3f7ca110ba057ec2180165a17f7e662ae376b273999d6"
}