Kieren Diment wrote:
Yeah, 98% of your browsers have javascript enabled and a big chunk of
the remainder are bots ...
On the other hand you might want a non-javascript undo option at the
other end if you go that route.
Oh, and watch out for a Classic Error I saw in someone's code a little
while ago..
They had entered a bunch of state-modifying buttons like this:
<a href="/blah/blah/$id/delete" onclick="confirm(..)"><img
src="/static/trashcan.gif" alt="Delete"/></a>
But what happens when your site gets spidered by a search engine, that
follows all links?
Whoops.
There's a good reason state-modification-actions should be POST (or
rather, non-GET, if you want to go with PUT, DELETE, etc)
On 22/01/2009, at 3:06 PM, Jonathan Rockway wrote:
* On Wed, Jan 21 2009, Dave Howorth wrote:
Paul Falbe wrote:
That works thank you very much. Don't know how many google searchs
I did
trying to find that out!
Rodrigo-51 wrote:
Paul, how about a javascript confirm() box?
... and if the user has Javascript disabled? ????
<noscript>Please enable Javascript. It's Two Thousand Fucking
Nine.</noscript>
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
