- 🇦🇺Australia mstrelan
I think the changes requested in #24 can be reverted now that we don't support IE anymore. As mentioned in #32 we still need to address #4.
- 🇦🇺Australia acbramley
Confirmed the issue still exists on 10.1.x. The same solution should be able to apply, but we need tests and a reroll as well as removing the local cache.
- Status changed to Needs review
about 2 years ago 10:58am 21 March 2023 Adding reroll for 10.1.x. Patch #27 throws the following error -
error: patch failed: core/misc/autocomplete.js:65
error: core/misc/autocomplete.js: patch does not apply- Status changed to Needs work
about 2 years ago 1:49pm 21 March 2023 - Status changed to Needs review
about 2 years ago 5:43pm 21 March 2023 - Status changed to Needs work
about 2 years ago 5:44pm 21 March 2023 - 🇦🇺Australia mstrelan
My suggestion in #38 was a little misguided. What I meant is that we can indeed use
includes
instead offind
. - Status changed to Needs review
about 2 years ago 4:06am 22 March 2023 - Status changed to Needs work
about 2 years ago 4:37am 22 March 2023 - 🇦🇺Australia acbramley
Here's a working fix with .includes. Still looking for existing JS tests for this widget but I don't think there are any.
- last update
over 1 year ago 29,672 pass - First commit to issue fork.
- Merge request !11553Issue #2186647 by rishabh vishwakarma, droplet, anmolgoyal74, nod_, rajneeshb,... → (Open) created by akalam
- 🇪🇸Spain akalam
I've created a MR with the changes of #79 to apply against D11 or D10.4. I've tested the patch locally and it works avoiding to display terms alreay applied when using an entity reference field with the widget "Autocomplete (tag style)"