I was thinking something more along the lines of the checkout process starts via an O.K. from javascript, thus printing the checkout screen. If the javascript does not return the O.K., namely javascript is disable, then a message is supplied. I don't know that this would be too hard, though there are probably a couple of different ways to pull this off.
Re: Re: Re: Re: Javascript in checkout process does not degrade
Mon, 12/17/2007 - 12:37
#1
Re: Re: Re: Re: Javascript in checkout process does not degrade
Javascript in checkout process does not degrade gracefully By: david.wabnitz@gmx.de (12 replies) Mon, 10/22/2007 - 08:33
- #12 By: sisko (04/03/2010 - 12:40)
- A kludgy solution to this problem By: BenStallings (04/20/2009 - 12:53)
- Re: Javascript in checkout process does not degrade gracefully By: Lyle (10/30/2007 - 13:17)
- shipping By: Fraser (10/24/2008 - 09:57)
- Re: shipping By: Fraser (10/24/2008 - 11:41)
- Re: Re: shipping By: Ryan (10/24/2008 - 11:47)
- Re: Re: Re: shipping By: slake (02/05/2009 - 13:48)
- re: shipping By: Fraser (10/24/2008 - 11:54)
- Re: Re: shipping By: Ryan (10/24/2008 - 11:47)
- Re: shipping By: Fraser (10/24/2008 - 11:41)
- Quote:Google Analytics says By: greenSkin (01/07/2008 - 14:59)
- Re: Re: Javascript in checkout process does not degrade graceful By: greenSkin (12/17/2007 - 12:19)
- Re: Re: Re: Javascript in checkout process does not degrade grac By: Ryan (12/17/2007 - 12:24)
- Re: Re: Re: Re: Javascript in checkout process does not degrade By: greenSkin (12/17/2007 - 12:37)
- Re: Re: Re: Javascript in checkout process does not degrade grac By: Ryan (12/17/2007 - 12:24)
- shipping By: Fraser (10/24/2008 - 09:57)

