fix(docs): disable Algolia Ask AI side panel to stop cookie widget overlap - #1218
Merged
Conversation
…erlap The floating Ask AI launcher (.DocSearch-SidepanelButton.floating) is pinned to the bottom-right corner, where it overlaps the GTM-injected cookie-consent widget. Disabling the side panel removes the redundant floating button; Ask AI remains available inside the search modal.
mateuszlampert
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The floating Algolia "Ask AI" launcher (
.DocSearch-SidepanelButton.floating) is pinned to the bottom-right corner, where it overlaps the GTM-injected cookie-consent widget. This setscustomFields.algolia.enableSidePanel: false, which removes the redundant floating button. Ask AI is still reachable from inside the search modal, so no functionality is lost.Introduces a breaking change?
Type of change
Tested on
Testing instructions
cd docs && yarn build && yarn serve(or run the deployed site, since the cookie widget only loads via GTM there).Screenshots
Related issues
Checklist
Additional notes
The cookie-consent widget is injected at runtime via the GTM container and is org-level, so the fix is applied on the Algolia side.