While working on the Rules UI I stumbled on a big issue:
drupal_html_id ensures that HTML IDs are always unique, even when forms are outputted multiple times on the same page. It does that, by appending a counter to the string(This was introduced here: #384992). So if your site replaces certain content using AJAX, all the IDs will be changed and that will cause problems to any JavaScript that wants to use an element, which finds it by its ID.
In my case, for example, the machine name script isn't able to find the input form, from which the label is read(but i think it also conflicts with the table drag script).
Reloading only certain parts of the form will probably not solve the issue(because of the table drags) and I'm certain there are many cases, which conflict with this issue in similar way.

CommentFileSizeAuthor
#3 label-gets-lost.jpg117.74 KBrobertdouglass

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Title: Ajax && (drupal_)html_ids » ajax reloads break existing HTML ids
Priority: Critical » Normal

yep, that's indeed weird. While drupal_html_id() is fine to ensure unique ids, it should not change the IDs of already previously existing elements - JS stuff often relies on IDs for finding HTML elements. However still the generated JS code should be able to deal with the generated IDs. Thus setting priority to normal.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

subscribe

robertdouglass’s picture

robertdouglass commented
StatusFileSize
new label-gets-lost.jpg117.74 KB

I wonder if this is related to the bug where Label fields get reset if you change the dropdowns while adding a field? (see screenshot)

casey’s picture

casey commented

@robertDouglass see #735204: vanishing label text from manage fields page

dawehner’s picture

dawehner
Primary language German
commented

Subscribe

Someone suggested to not rely on form id's anymore.

chalee’s picture

chalee commented

Has a solution or at least a temporary fix found for this issue?

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Closed (duplicate)

Basically, you can't use HTML IDs any more for targeting things in CSS or JS. You have to use something else.

I'm going to call this a duplicate of #1305882: drupal_html_id() considered harmful; remove ajax_html_ids to use GET (not POST) AJAX requests

chalee’s picture

chalee commented

@rfay: What is that 'something else' that we can use. I tried to use classes e.g 

$('.some-class .form-select').change()

and HTML attributes like name e.g

 $('select[name='field-name[und]').change()

but all in vain. Please help.