Yes, the problem comes on load (and click) when assigning/using a listener to/on the boxchecked hidden input box, which is the way the js registers that a box has been checked (of course).
That's because I have two lists, each needing separate boxchecked elements (otherwise checking a box in one list would enable not only its own button but also buttons referring to the other list.
It seems to me that is because I've used the usual J! trope of one form element for the whole page with tabs inside it (my lists are in different tabs).
Is it acceptable to have multiple form blocks on the page? Most would be inside tabs, but the search bar isn't in a tab and presumably would need its own...
That's because I have two lists, each needing separate boxchecked elements (otherwise checking a box in one list would enable not only its own button but also buttons referring to the other list.
It seems to me that is because I've used the usual J! trope of one form element for the whole page with tabs inside it (my lists are in different tabs).
Is it acceptable to have multiple form blocks on the page? Most would be inside tabs, but the search bar isn't in a tab and presumably would need its own...
Statistics: Posted by MarkRS — Thu May 02, 2024 9:15 am