Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The id for the "Go" button is "edit-submit." This happens to be the same id as the node edit form, which means you get a validation error when you run masquerade on a node edit form. That's not the end of the world, but as one who has spent 45 minutes trying to figure out why my javascript event handlers can't be applied to the submit button, I'd suggest this be changed.
Comment | File | Size | Author |
---|---|---|---|
#3 | masquerade-id-conflict-856620-3.patch | 369 bytes | mgifford |
Comments
Comment #1
hefox CreditAttribution: hefox commentedConsidering form_clean_id, relying on an ID for a form element is, well, asking for trouble.
though, it's odd that the id's are the same; one ID should be edit-submit-1, but it could be due to something (views I think?) flushing the form_clean_id cache between node form and masquerade form creation.
Comment #2
dpearcefl CreditAttribution: dpearcefl commentedThis is still happening. I'll be happy to submit a patch if we can agree on what the id should be.
Comment #3
mgiffordSo something like this should resolve this.
Comment #5
nvahalik CreditAttribution: nvahalik at Code and Salt commentedThis no longer appears to be the case as the
#id
is not defined explicitly and on pages where anotheredit-submit
is defined, it correctly has another ID.