Unless there are special circumstances I don't understand, I think it is safe to require basic JavaScript support on the client for pretty much any web site. I don't see more of a technical issue to discuss.
However, it sounds like your superiors want that functionality anyway. I'd try to discuss with them and understand their needs. On the other hand, if they aren't willing to discuss it or explain it, or they are determined to have that feature, then within the scope of your employment it's really not your choice and you should do they need you to do. On Sep 29, 7:30 am, Rakesh <[email protected]> wrote: > Hi folks, > > I would be interested in experiences/opnions about supporting non JS. > > My current. commercial, company insists that we need to maintain non JS > functionality on our site. What this has done is complicate enormously the > front end and the back end. > > Going forward I would like to propose moving our architecture to GWT but > that would mean losing non JS support (but gaining so much more in other > areas). > > What do others do? Maintain a separate site? Choose not to support non JS > browsers (perhaps showing a page to call instead)? > > BTW, according to the stats we make zero sales from non JS visitors - and it > seems all the visitors are from our won testing dept!!! Somehow the upper > levels of business have got it into their heads that non JS version of our > site is mandatory (maybe even illegal not to do so). > > Thanks > > Rakesh -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
