-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This breaks the Location set to Relative to element #24
Comments
@prolitariat Thanks for the video! So, this is a CSS issue which has an easy fix for individual use cases, but a much more complex fix to handle all cases like this. The short explanation is the Pendo guide container positioning is calculated dynamically based on the guide container height (ie, the contents that are inside the guide). Since the height is calculated before the code block code executes, Pendo places the guide where it should be if the invisible objects are present: Screen.Recording.2023-01-10.at.9.59.15.AM.movThe quickest way to fix this would be to hardcode the height like so (you may need to adjust the pixel height):
I'll chat with our product team -- it's long overdue for us to support multi-select checkboxes out of our product, so that will determine whether or not I implement a more scalable hack-fix. |
Appreciate the quick reply! :) So, the solution is to hardcode a set height for all guides under the global CSS settings? anyway to add a line of CSS to ignore specific criteria set by custom code blocks? |
Hmm, unfortunately, there's not a way to selectively ignore parts of a code block without modifying the JS of each one. I did think of a quicker way to force set every guide step at the bottom right of the page though -- try adding this to the bottom of the JS, after the checkbox snippet:
You can change the distance from the bottom accordingly based on the height of your RC badge. This will logic the guide step into the same spot each time after rendering. |
Relative to element location settings don't function when this is enabled, deleting the custom code snippet resolves issue.
The text was updated successfully, but these errors were encountered: