Currently, the disabling of disallowed select elements and checkboxes (terms for which the user does not have create) is done only via jQuery, because of core FAPI limitations.

Relevant core issues:

The form is still fully functional with JavaScript disabled; disallowed changes are silently ignored. Therefore, I consider this a task and not a bug. However, there is a usability issue because users without JavaScript support have no indication that they cannot actually change certain elements, and they might become confused or not even realize their changes to these elements are not being used.

Once the FAPI limitations are resolved, we can provide proper FAPI handling for these elements, but a workaround would be a good idea in the interim. One possible workaround would be to unset the disallowed options entirely, then add back any that should be displayed via jQuery.

Comments

xjm’s picture

Issue tags: +TAC UX

Tagging.