Closed (fixed)
Project:
Linkit
Version:
8.x-5.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 Aug 2017 at 12:23 UTC
Updated:
26 Nov 2017 at 00:04 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
anonAre you sure the throbber is missing? Linkit has CSS for this.
Would be interesting to know if this can fail, and if, why it fails.
Comment #3
anonSee this image from my installation. It is Linkit 8.x-5.x
Comment #4
anonThis issue were added in the dev branch. Might be the same problem.
#2871331: Throbber icon not found on subdirectory base installations
Comment #5
berdirYes, relying on core files in CSS is not possibly, just copy that over into the module and then use it like that. A bit unfortunate but there is no other reliable way.
Comment #6
anonThen I will consider this as fixed/duplicate as of #2871331: Throbber icon not found on subdirectory base installations.
Should be in 8.x-5.0-beta6
Comment #7
berdirNope, that issue *introduced* this problem, when you have the module in e.g. /modules/contrib/linkit and not just /modules/linkit, as the last comment/patch in that issue also mentioned.
Neither approach works for both cases, the only thing really is to copy the file and point to that.
Comment #8
anonAh, sorry for this. I misunderstood you.
Comment #9
berdirNo worries, I was not very clear.
Updated the title and tagging as novice, all that needs to be done is copy the file from core into this module and update the CSS.
Comment #10
anonHow about this? Seems like we can use the core class for autocomplete fields (form-autocomplete).
The only risk I see here is that someone might use a theme where the autocomplete-loading.module.css is not loaded. Is that something we can live with or do we really need to make a copy of the throbber icon and duplicate the css?
Comment #11
berdirSeems like a nice solution, not tested yet.
I guess if they do leave that out then all autocomplete form elements would be broken. This even seems better in that regard, because it a) gives themes a single way to style all autocomplete elements and b) it's at least as likely if not more that themes skip all module CSS files I'd say.
So, +1 from me.
Comment #12
anonGreat! Thanks for input.
I would appreciate if you could test the patch, and give me feedback. Then I will commit this right away.
Comment #13
berdirWorks nicely for both wysiwyg integration and the not yet committed link field integration, yay form elements :)
Comment #14
anonRunned the tests and we have some Javascript errors now.
Turnes out that if we add the "form-autocomplete" class, the default Drupal autocomplete script will kick in, which is not desirable for us.
Comment #15
anonSeems like the only solution is the one that have already been discussed, to copy the image files into the module.
Comment #17
anonI don't manage to create a patch with the new image files in it that will work in the testbot.
Comment #18
mbovan commentedA try to create a patch with images.
Comment #19
anon@mbovan: Seems to work with the test bot. Please let me know how you created the patch file.
Comment #20
mbovan commentedI used
git diff --binaryoption.It looks like your patch was missing "new file mode" part: https://www.diffchecker.com/aEanzIxQ
Comment #21
berdirThe autocomplete.js change seems a bit unrelated but otherwise this seems OK.
Comment #22
acbramley commentedApplying the patch from #18 with
patch -p1orgit applydoesn't actually add the images in.Comment #23
acbramley commentedTested again and git apply seemed to work, not too sure why it didn't the first time. Sorry!
Comment #25
anon