Re: [PEPr] Comment on HTML::HTML_QuickForm_advmultiselect

I don't think follows very well your mind way. What you expected to have : 1. an alternate way for browser that have js disabled ? 2. another way to manage both lists ? you wrote : " ... Client-side JS switch visibility for the select elements. ..." Please explains me , i've some doubt ! Laurent Philippe Jausions wrote:

Laurent Laville wrote:

Laurent Laville (http://pear.php.net/user/farell) has commented on the proposal for HTML::HTML_QuickForm_advmultiselect. Comment: Philippe, I think that non-js browsers (or js disabled) is a problem for all web application. Even if it's a huge limitation, i can understand that some people are anxious (security reasons perharps) to let js active. This QuickForm element has a *ugly* solution to solve the js disabled. I 'll let you introduce it. It's requires more programmation than just the default behaviour. If end-user keep its selection active without validate (click on) "add" or "remove" buttons: * on left select box, then the element prefixed by two "_" will be transmit when the form will be submit. * on right select box, then the element prefixed by one "_" will be transmit when the form will be submit. Try with any of live demos, and you'll understand what i means.

I agree that voluntarly turning off JavaScript is a bit extreme, and by the same token we can't support antic web browsers, such as Mosaic for those who remember ;-) But since you're using JS and CSS styles, why not doing something like this (from your 1st example) 1. cars[] select element is visible, 2. _cars[] and __cars[] are invisible, 3. Client-side JS switch visibility for the select elements. I haven't look deeply into your code, but do you think that could work? -Philippe