position: relative causes component position to be wrong #441
Comments
|
I think we could get rid of |
sapegin
added a commit
that referenced
this issue
Jun 8, 2017
## New features ### UI refresh Welcome our refined UI! More consistent and clean:  🦊 This is the first part of the planned improvements and a base for upcoming plugin API, see #426 and #354 for more details — we need your feedback there 🚀 🍕 Thanks to @SaraVieira and @n1313 for help! ❤️ ### Props & methods are hidden by default Use the new config option [showUsage](https://react-styleguidist.js.org/docs/configuration.html#showusage) to restore the old behavior. ## Bug fixes ### Crash when using a defaultProp that is not listed in props (#437 by @ankri) ### Isolated examples inside sections ### Issues with `position: relative` (#441) ### Ugly isolated example link (#235)
sapegin
added a commit
that referenced
this issue
Jun 8, 2017
## New features ### UI refresh Welcome our refined UI! More consistent and clean:  🦊 This is the first part of the planned improvements and a base for upcoming plugin API, see #426 and #354 for more details — we need your feedback there 🚀 🍕 Thanks to @SaraVieira and @n1313 for help! ❤️ ### Props & methods are hidden by default Use the new config option [showUsage](https://react-styleguidist.js.org/docs/configuration.html#showusage) to restore the old behavior. ## Bug fixes ### Crash when using a defaultProp that is not listed in props (#437 by @ankri) ### Isolated examples inside sections ### Issues with `position: relative` (#441) ### Ugly isolated example link (#235)
|
Should be fixed in 5.4.0. |
This was referenced Nov 5, 2022
This was referenced Dec 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, thanks for this awesome project!
I'm writing a hovercard component that uses absolute positioning. When rendering it in a styleguidist example, the component breaks, because it takes its initial position values from a parent div with
position: relativespecified. (http://i.imgur.com/Q4iwmIT.png)Any suggestions as to how to get around this? Thanks again!
(To give more context, here's what it looks like 'broken': http://i.imgur.com/UCwxeKd.png. You can see the offset is being calculated from the parent div, rather than the body as expected.)
The text was updated successfully, but these errors were encountered: