[whatwg] Proposal for a link attribute to replace <a href>
Tab Atkins Jr.
jackalmage at gmail.com
Thu Feb 28 12:24:18 PST 2008
On Thu, Feb 28, 2008 at 1:44 PM, Paweł Stradomski <pstradomski at gmail.com>
> W liście Robert O'Rourke z dnia czwartek 28 lutego 2008:
> > Paweł Stradomski wrote:
> > <div class="steps">
> > <input href="/basket.html" class="basket-step" value="Basket" />
> > <input href="/checkout.html" class="current checkout-step"
> > value="Checkout" /> <input type="submit" class="confirm-step"
> > value="Confirm" />
> > <input type="button" disabled="disabled" class="payment-step"
> > value="Payment" /> </div>
> > If I could use one (or at least fewer types) of elements it would make
> > cross-browser styling easier.
> You're breaking element semantics here. <input>s are for form input
> elements -
> text fields, checboxes etc. The above would make those inputs text fields,
> you didn't spcify the type. Now how can an input be a link? It's supposed
> accept user text, not to point to some other resource. Activating an input
> (by clicking on it etc.) should just make it start accepting typed text,
> make the browser jump somewhere else.
> Presentation/style should follow the semantics, not the other way round.
> After more thinking I lean towards Krzysztof's point of view, href as
> attribute is a bad idea. I guess it's in the FAQ for a purpose, so EOT for
> (of course I'll accept and respond to off-list e-mails).
> Paweł Stradomski
Nod to Pawel. A workaround would be to custom-style your buttons so that
you can match the links to their appearance. I override default button
patterning completely in my pages for precisely that reason (also so they
fit in the color scheme better). It's easy enough to style a link in the
same fashion (easiest of all when you have proper inline-block support).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg