Problem/Motivation
When using the linkit, it is possible to use linkit also on the link button in CKEditor. In this case, the default link field is replaced with an autocomplete field. The results window has a maximum size; if many results are returned by linkit, a scrollbar is displayed.
This does not work when using Claro as the admin theme, as the scrollbar is hidden. Hence, only the first 8 / 12 results are displayed to users; all the other results are hidden.
Steps to reproduce
- Install drupal vanilla, select Claro as the admin theme;
- Install linkit, enable the module and enable it also in the "CKEditor plugin" section of the Content authoring --> Text formats and editors page;
- Create a bunch of nodes, e.g. 20 articles
- Try to create a link via ckeditor, from any node.
The results will be displayed like this:

Proposed resolution
Remove overflow: hidden in .ui-autocomplete.
User interface changes
The scrollbar will now be displayed also for autocomplete fields.
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | 3219921-D9-3.patch | 939 bytes | javi-er |
| #16 | drupal-core-issue-3219921-test-OK.png | 95.8 KB | mchameddie |
| #15 | 3219921-D9-4.patch | 943 bytes | kostyashupenko |
| #15 | 3219921-D10.patch | 993 bytes | kostyashupenko |
| #11 | 3219921-patch-6-after-edge.png | 978.04 KB | javi-er |
Issue fork drupal-3219921
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3219921-claro-display-the
changes, plain diff MR !821
Comments
Comment #3
nironan commentedFirst try; I just removed the overflow: hidden clause. Raised against 8.9, not sure if it should also be raised against 9.3
Comment #4
gauravvvv commentedPlease make changes in .pcss file then compile the code to css. Don't write directly in css file.
Re-rolled patch #2, Added interdiff for same.
Comment #6
jens.de.geit commentedRe-roll of patch 4
Comment #8
lauriiiComment #9
timohuisman#6 worked for me on 9.3. Tested in Safari 15.1 and Chrome 97.0.4692.99.
Comment #10
gauravvvv commentedComment #11
javi-er commented#6 works for me too on 9.3 on Chrome, Safari, Firefox and Edge, screenshots below:
Before:
After:
Chrome

Firefox

Safari

Edge (browserstack)

Comment #12
javi-er commentedComment #13
kristen polThanks for testing @javi-er. I'm reviewing this issue even though it's marked RTBC because it was left open in a browser tab from a couple days ago :D
1. Patch in #6 passes tests for 9.3 but not 9.4.
2. Fix is simple and only addresses the issue in the issue summary.
3. Not sure if automated tests can be added for this.
4. Manually testing on 9.3 was successful.
I think this has to be fixed in 9.4 first, so moving back to "Needs work" for getting that patch working, but I'll check in with bugsmash team too.
I also updated the issue summary proposed resolution to reflect the patch.
Comment #14
kristen polBased on feedback from xjm in Slack, we either need:
1. Separate patches for 9.3, 9.4, and 10.
or
2. Patch for 10 that gets committed and then we back port to 9.4 and then 9.3.
Comment #15
kostyashupenko3219921-D9-4.patchpatch can be applied now to Drupal 9.3.x normallyComment #16
mchameddie commentedSuccessfully tested the D9.4.x patch at Florida DrupalCamp 2022:
Screen capture attached.
Comment #17
mchameddie commentedAttempted to review the D10 patch at Florida DrupalCamp 2022.
There is currently no Linkit version available for D10.
Comment #18
kristen polThanks for testing! Tagging for Florida Camp.
Comment #19
kristen polConfirmed the patch in #16 still applies to 9.3 and 9.4 but not to 10 (for
content-header.css, see below).IMO even though there is no D10 Linkit module yet, a patch could be created for this since the change is so simple. We might be able to test by updating the Linkit module info file and marking it for D10 and installing Backwards Compatibility and seeing if it just works :)
This can also be tested on 9.3 just to be safe.
Comment #20
kostyashupenkoPatch for D10 applies clearly now.
@kristen-pol in those patches there is no changes for
content-header.pcss.cssat all, it looks like you tried to apply wrong patch (since no idea what is1732.diffin yourpatch -p1 < 1732.diffComment #21
kristen polWhoops. Was working on too many issues simultaneously in different tabs. Apologies for the noise.
Indeed,
3219921-D10.patchapplies cleanly to Drupal 10 and3219921-D9-4.patchapplies cleanly to both Drupal 9.3 and 9.4.Rewording the only relevant part of #19:
1. The 9.4 patch can also be tested on 9.3 just to be safe.
2. Even though there is no D10 Linkit module yet, we can probably test by updating the Linkit module info file and marking it for D10 and installing Backwards Compatibility and seeing if it just works :)
Comment #22
kristen polForgot to tag for testing per #21.
Comment #23
javi-er commentedAdding patch for 9.3.x
Comment #24
kristen polThanks @javi-er but the 9.4 patch in #15 was applying cleanly to 9.3 as well as noted in #21.
9.4 was tested in #16.
Now only Drupal 10 needs to be tested. This cannot be committed to 9.4 until the the Drupal 10 patch is tested. See explanation in #21 on how to possibly hack Linkit to test this.
Comment #25
andy-blumTried to squeeze in the D10 review before end of day today, but Linkit needs more work. Here's the issue if anyone wants to try to patch linkit AND D10 to test.
Comment #26
ckrinaIn the last Claro meeting we agreed we'd apply the fix for 9.4 to D10 too without testing for now due to the difficulty to do that, since we can't right now without a D10 Linkt version. If we see we need a different fix for D10 we'll open a new issue for that once we know how to reproduce it.
I've just tested the 9.4 and 9.3 patches with Linkit and they apply cleanly and solve the problem. Also, the code solution looks good for me. Marking as RTBTC.
Comment #30
lauriiiCommitted 5061005 and pushed to 10.0.x. Also committed patches to 9.4.x and 9.3.x. Thanks!