- From: Dmitry Turin <html60@narod.ru>
- Date: Fri, 9 Nov 2007 09:14:24 +0200
- To: public-html@w3.org
Julian, >> If we're going to talk about user intentions, we have to accept the fact >> that most users have no idea how GET and POST differ, see no difference >> between clicking on a link and a button, and wouldn't be able to tell >> apart: >> <a href="http://www.example.com" >> style="color: black; text-decoration: underline">Click me</a> >> and >> <form action="http://www.example.com" method="POST"> >> <input type="image" >> style="color: black; text-decoration: underline" >> alt="Click me"> >> </form> JR> My experience is that most people do understand the difference between a JR> link and a button. JR> Also, the fact that it's possible to *obscure* that isn't a good JR> argument in favor of adding more stuff like this. On the contrary, we JR> should educate web designers that it's a bad thing to make something JR> look like a link when it isn't. I'm sure, that the best variant, when <a> behaves similar <form>. I'm sure. But this can require unification of HTTP for both cases. Dmitry Turin HTML6 (6.5.0) http://html60.euro.ru SQL5 (5.7.0) http://sql50.euro.ru Unicode7 (7.2.1) http://unicode70.euro.ru Computer2 (2.0.2) http://computer20.euro.ru
Received on Friday, 9 November 2007 07:14:29 UTC