-
Notifications
You must be signed in to change notification settings - Fork 939
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
Mount InfoBox content and OverlayView content directly to their respective DOM #93
Comments
Thanks for the great discussion and open an issue for me! Will try to add a PR soon :) |
Feel free to submit a PR. Close for now We're also looking for maintainers. Involve in #266 to help strengthen our community! |
I know this issue is super old, but could you provide some more insight into what the proposed solution is for removing the unneeded I understand that you probably haven't thought about this since the day the issue opened, but I'd love to contribute to fix this but want to make sure I head down the right path. |
@Jamez14 you might be able to apply the z-index to the child div that you have control over; if not, check the |
I should've just tried to apply it to the child |
Right now, an empty, otherwise useless, div is used to account for the fact that React needs to render to a DOM element. There's actually access to the underlying InfoBox/OverlayView div under
instance.div_
which will eliminate the need for that React "crutch".The text was updated successfully, but these errors were encountered: