Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Learn More

Double click now required to use survey response buttons - why?

more options

If you click on a response button in a Benchpoint survey, the answer defaults to the first choice on the response list. A Double click is now required to hit the right choice.

This is confusing respondents who have been used to a single click for years.

What re-coding information can you give us? The URL below is a sample survey which demonstrates the problem in (Firefox 4 only) Thanks

If you click on a response button in a Benchpoint survey, the answer defaults to the first choice on the response list. A Double click is now required to hit the right choice. This is confusing respondents who have been used to a single click for years. What re-coding information can you give us? The URL below is a sample survey which demonstrates the problem in (Firefox 4 only) Thanks

Všetky odpovede (3)

more options

This is related to the new HTML5 parser in Firefox 4. It is a bit stricter than the parser in Firefox 3.6. You can confirm the difference by toggling the parser off.

(1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the filter box, type or paste html5 and pause while the list is filtered

(3) Double-click html5.parser.enable to toggle it to false (it will turn bold).

Then reload the problem survey page and test again.

I think the problem is that there is a label tag around the entire table containing the radio buttons. If you choose View Source, press Ctrl+f, and search for <label><table you will see what I mean.

To test the effect of removing those label tags, you can copy this bookmarklet and paste it to the address bar on a survey page and press Enter to run it.

javascript:var lt=document.querySelectorAll("label > table"); for (i=0;i<lt.length;i++){p=lt[i].parentNode; p.parentNode.insertBefore(lt[i], p); p.parentNode.removeChild(p)}; void 0;

That fixes it for me. Does it work for you?

more options

Thanks for your help. I am not a programmer, but what you say makes sense. This application runs on quite old code. I guess we need a .net programmer to edit the code. Is that you, by any chance? You can contact me offline -gaunt@benchpoint.com. Thanks again

more options

I've never learned .Net (nor am I a professional programmer).

As a short-term workaround, your web people might be able to modify the /optima/utilities.js file to run the above snippet to remove the labels around tables. (E.g., by running it after a short delay after the page loads using window.setTimeout().) I think if you give them a link to this thread, they would be able to set that up fairly quickly.