Open nightspite opened 10 months ago
@nightspite This is great. Thanks! Flex is the way to go.
Yeah it seems to apply this styling in certain layout render modes:
Disabling the height
and overflow
property fixes it. But why were these props there in the first place?
But looking the age of this issue...
I'm not sure why it's positioned outside/below the box in this situation. Will look into it when I have some time. Currently working on v5 which won't have this issue.
I'm not sure why it's positioned outside/below the box in this situation. Will look into it when I have some time. Currently working on v5 which won't have this issue.
I get that, no problem ;) Maybe I can fix things, but where can I find examples of the Filepond instances in compact and integrated modes?
@bbredewold Appreciate the offer. Have to admit that these aren't well documented.
It's controlled with the stylePanelLayout
referenced in the property table on this page, I've copied it below:
Set a different layout render mode. Can be either
'integrated'
,'compact'
, and/or'circle'
. Compact mode will remove padding, integrated mode is used to render FilePond as part of a bigger element. Circle mode adjusts the item position offsets so buttons and progress indicators don't fall outside of the circular shape.
The circle mode can be seen on the homepage, it's the profile picture example. I don't think I have an example of the integrated mode, but it's apart from some margins I believe it's very similar.
Is there an existing issue for this?
Have you updated FilePond and its plugins?
Describe the bug
The bug that I have found is causing all elements below the dropzone to not be clickable. It's caused by one of 2 things: either z-indexes or the way of positioning the elements needs to be changed.
.filepond--list-scroller has a height of 100% (so it inherits from the parent -> 76px) & it's translated by 76px, so it looks like on the screenshot below. Because of that the z-indexes on child elements are not playing along with the other elements on the page.
A simple solution, that I'm currently using is changing
position: absolute
&transform: translate3d()
to just flex layout.Reproduction
I am using the React library, but the problem refers to styling, so I though creating the issue in the main repo is the way. But the setup using React looks like that:
Environment