The Difference Between a Button and a Link
The article explains the proposed addition of action and method attributes to HTML buttons and why this matters. It contrasts the semantics of buttons, which trigger actions in a fixed browsing context, with links that represent navigable destinations and support re‑contextualization features. The author argues that navigation should use buttons when the action cannot be re‑contextualized, and provides examples of appropriate button usage.
- ▪The Triptych Project proposal seeks to add action and method attributes to the <button> element to enable more powerful form interactions.
- ▪Links represent destinations and allow users to open, copy, bookmark, or share them in various contexts, while buttons lack these affordances by design.
- ▪Buttons trigger actions within the current browsing context and cannot be middle‑clicked or saved like links, making them suitable for fixed‑context operations such as form submissions or logout actions.
- ▪Navigation should be implemented with buttons when the action cannot be re‑contextualized, such as editing or deleting content, whereas links are appropriate for destinations that can be opened or shared elsewhere.
Hacker News (Front Page) files mainly under programming. We currently carry 734 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Unplanned Obsolescence |
| Canonical URL | https://unplannedobsolescence.com/blog/buttons-vs-links/ |
| Publication time | Wed, 29 Jul 2026 00:12:14 +0000 |
| Retrieval time | 2026-07-29T00:46:08.194Z |
| Last seen | 2026-07-29T00:46:08.194Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | V4x0u-d3kpnL · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Unplanned Obsolescence Home Blog Talks About RSS The Difference Between a Button and a Link July 28, 2026 Of the three proposals in the Triptych Project, my multi-year odyssey to add a few small-but-powerful features to HTML, the one that generates the most questions is Button Actions. The proposal itself is very straightforward: we want to add the action and method attributes to the button. <button action="/begin" method="GET">Start</button> Button Actions are such a simple primitive that people often ask why they’re needed. The answer rests on a distinction that web users intuitively understand but rarely have to think about directly: the difference between a button and a link.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Unplanned Obsolescence.
Discussion
0 commentsMore from Unplanned Obsolescence
