-
Notifications
You must be signed in to change notification settings - Fork 266
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
Wrapperless cell editor #123
Comments
Another vote for this! |
Yes this can be added, we cant get rid of the wrapper entirely but we can unstyle it. |
That works for me! One other issue I've been running into is needing more editor space below the cell. Currently there's a |
What do you want that to do? Currently it stops the cell editor going off screen |
I think in the ideal world, if the child wants to grow, it would scroll the table so that the top of the editor still lines up with the cell but the bottom of the editor isn't cut off, but that seems overly complicated. Maybe the editor could specify an anticipated max-height and the table will try to scroll that extra amount when you go to edit? For now I think I can work around it using I'll give some more thought on what would be best here |
Fixed in 3.3.0 |
I'm building a custom cell editor using the
provideEditor
attribute, but it seems that this enforces that the editor gets put inside aDataGridOverlayEditorStyle
andclip-region
div which adds its own border, border radius and stylesinput
andtextarea
elements.glide-data-grid/packages/core/src/data-grid-overlay-editor/data-grid-overlay-editor.tsx
Lines 108 to 117 in 6b0a04f
Would it be possible to support a version of provideEditor that handles its own borders to allow for more flexibility?
I see that I can add a
disablePadding
property to remove the padding, but it would be great if there was another attribute that could remove some of this other styling too.glide-data-grid/packages/core/src/data-grid-overlay-editor/data-grid-overlay-editor.tsx
Lines 71 to 82 in 6b0a04f
The text was updated successfully, but these errors were encountered: