Closed (fixed)
Project:
Search API Autocomplete
Version:
8.x-1.0
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Sep 2018 at 17:20 UTC
Updated:
4 Oct 2018 at 05:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
chintan.vyas commentedAttaching the patch for improving accessibility for search results.
Comment #4
mikemadison commentedComment #5
mikemadison commentedComment #6
mikemadison commentedthe suggested template change doesn't resolve the underlying issue here (thanks @chintan.vyas for setting me straight). i think we need to update the associated test to use the solution in #2 to get the suggestions working properly.
Comment #7
drunken monkeyThanks for reporting this problem!
The fail in #2 wasn’t a problem of the test, though, but with the patch: this not only changes the format when a URL is used, but also for normal autocomplete suggestions, resulting in incorrect behavior. The attached patch should fix this.
Also, if we can just set a
urlkey on the autocomplete suggestions, why should we still bother with the leading space? (Didn’t realize this was possible.)Not 100% sure this doesn’t constitute a BC break, though, changing the format like that. But hopefully this won’t affect too many people. And the format would be a lot cleaner going forward (not relying on the leading space).
Anyways, revised patch attached, please test/review!
Comment #8
chintan.vyas commentedReviewed and tested #7 on local using Chromevox extension. Search result announcement is working fine.
Comment #9
mikemadison commentedworks great for me
Comment #11
drunken monkeyGreat to hear, thanks a lot for testing!
Committed.
Thanks again for your work in this issue, both of you!