2 ms·
I'd put it like this: If there is an html element that describes the thing perfectly, use the same styling as html, or better - use the element itself. If it's
by anonymous 13y ago
I'd put it like this:
If there is an html element that describes the thing perfectly, use the same styling as html, or better - use the element itself. If it's an <a>, it's a link, if it's an <input type=submit>, it's a button.
If it's not a plain html element and causes parts of the page to change via javascript, it's probably a button. Except if it functions exactly like a link, or in some weird edge cases, like if you're building a text-only site thing.
Or shorter:
In that same context, can you replace the text with:
- "release the kraken" -> button
- "information about krakens" -> link