Kevin Brown-Silva

Are shadow DOMs allowed to have duplicate IDs? I know that the root DOM object isn't allowed to have duplicate IDs per the HTML spec, but I'm not super familiar...

A change was introduced in https://github.com/ivaynberg/select2/commit/55827b9159cca41c94c2a232f49943cef602e52b that requires that Select2 is explicitly disabled using the attribute instead of the sizzle `:disabled` selector. A pull request is welcome that fixes this...

This should be fixed in 4.0. If it is not fixed, please add a :+1: to the ticket to bring it to our attention. Please also include an example that...

Yup, looks like this is still an issue. We are going to need to figure out what check Sizzle used to use to determine the disabled status of an element....

> Is this intended? Yup, totally intentional. https://github.com/select2/select2/commit/395e06aff52059f654aff47f03a26cad8955a092 > Would be nice to have an option to disable it if that is the case. I'm not sure how I feel...

Reopening this while we decide how best to handle this.

> Hey could someone by chance (@kevin-brown) explain if there's a way to override the Search.searchRemoveChoice without forking the repo? You can patch this method (not totally recommended but it...

Just going to note that a patch is available for this in https://github.com/select2/select2/issues/3354#issuecomment-132389291. The problem with the search box being cut off was fixed in 4.0.1.

This appears to be a common problem. Making this the primary ticket to track the issue. https://github.com/select2/select2/issues/5267 https://github.com/select2/select2/issues/5252 https://github.com/select2/select2/pull/5268 https://github.com/select2/select2/issues/5271

> But i cannot understand how this line works, so i cannot decide if it can be deleted ;( Unfortunately it can't be deleted. That line allows for Select2 to...