On 4 mar, 17:40, Chris Lercher <[email protected]> wrote: > Hi Thomas, > > according to Mariyan's description, the words should be embedded in > the text, so I assume, that they should look like links (color, > underline) and feel like links (mousepointer, ...) I would find it a > little bit odd to use spans, only to redecorate them using CSS to make > them look like hyperlinks. From the user's perspective, they should > work like hyperlinks - the use case basically doesn't change, if the > action is executed by a request to the server side or not. (Also, > there have always been in-page links "#...", so not every link has to > create a request to the server.)
By definition, a link triggers "navigation" (to another page or another place inside the same page). If your "link" points to "#" (as the "Options" in Google Groups) or "javascript:" or "javascript:void(0)", then it's not a link, just a button that looks like a link (much like the "Report spam", "Reply", "Edit Subject" etc. on Google Groups: the action is not "go to X", so it's a "action button", not a link). > Of course, it's also ok to use spans, actually they can be used for > everything in an HTML page, as long as CSS is enabled, so... raises > the question what HTML is good for anyway. You could also use <b> or <mark> instead of <span>. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
