Treat buttons like links
Daniel Pfeiffer
a long standing grievance I have with buttons is the arbitrary difference in
handling from links, even though as a user experience both do the same thing,
usually open a new page. I think consistency in handling is extremely important!
[I know that technically <form> and <a> is not the same thing, but as a user
why should I care about such lowly details...]
I want to be able to middle-click a button to get the result in a new page
(especially since some sites manage to go back to an empty form, making me
retype everything). Also I sometimes want to be able to bookmark a button
(along with any post data).
On a related note, javascript:-links usually fail when middle-clicked. That's
annoying because I don't always check the destination URL, so I get an empty
page, have to close it, and click again. The least you could do, is
implicitly duplicate the tab, if you find the javascript needs this context.
coralament / best Grötens / liebe Grüße / best regards / elkorajn salutojn
Daniel Pfeiffer
--
lerne / learn / apprends / lär dig / ucz się Esperanto:
http://lernu.net / http://ikurso.net
Jorgen Grahn
> Hi,
>
> a long standing grievance I have with buttons is the arbitrary difference in
> handling from links, even though as a user experience both do the same thing,
> usually open a new page. I think consistency in handling is extremely important!
>
> [I know that technically <form> and <a> is not the same thing, but as a user
> why should I care about such lowly details...]
>
> I want to be able to middle-click a button to get the result in a new page
> (especially since some sites manage to go back to an empty form, making me
> retype everything). Also I sometimes want to be able to bookmark a button
> (along with any post data).
>
> On a related note, javascript:-links usually fail when middle-clicked. That's
> annoying because I don't always check the destination URL, so I get an empty
> page, have to close it, and click again. The least you could do, is
> implicitly duplicate the tab, if you find the javascript needs this context.
Maybe that should go in opera.wishlist? (Try to sound a bit less
angry, though.)
I agree completely. I too know the difference, and yet it happens
almost daily that I sit with a button before me and go "oh, I wish I
could middle-clich that one!". For example, the poll voting button on
Slashdot's front page.
Or the other way around -- things which look a bit like buttons, yet
you can middle-click them if you remember in time that it works. Like
the article/discussion/edit tabs in a Wikipedia article.
Same thing with javascript links, I think. That's the ones which come
up as blank pages, right?
/Jorgen
--
// Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
Jan van Gent
> On Tue, 2009-12-15, Daniel Pfeiffer wrote:
>> Hi,
>>
>> a long standing grievance I have with buttons is the arbitrary difference in
>> handling from links, even though as a user experience both do the same thing,
>> usually open a new page. I think consistency in handling is extremely important!
>>
>> [I know that technically <form> and <a> is not the same thing, but as a user
>> why should I care about such lowly details...]
>>
>> I want to be able to middle-click a button to get the result in a new page
>> (especially since some sites manage to go back to an empty form, making me
>> retype everything). Also I sometimes want to be able to bookmark a button
>> (along with any post data).
Shift leftclick?
Works here.
Jan
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
