Skip to content
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

fix: Floating panel and dialog bugs #4708

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

fix: Floating panel and dialog bugs #4708

wants to merge 5 commits into from

Conversation

kof
Copy link
Member

@kof kof commented Jan 3, 2025

Description

Steps for reproduction

  1. click button
  2. expect xyz

Code Review

  • hi @kof, I need you to do
    • conceptual review (architecture, feature-correctness)
    • detailed review (read every line)
    • test it on preview

Before requesting a review

  • made a self-review
  • added inline comments where things may be not obvious (the "why", not "what")

Before merging

  • tested locally and on preview environment (preview dev login: 0000)
  • updated test cases document
  • added tests
  • if any new env variables are added, added them to .env file

@kof kof requested review from TrySound and johnsicili January 5, 2025 13:22
@kof kof marked this pull request as ready for review January 5, 2025 13:22
@@ -92,7 +92,7 @@ export const ValueEditorDialog = ({
title="CSS Value"
placement="bottom"
height={200}
width={Number(rawTheme.sizes.sidebarWidth)}
width={parseFloat(rawTheme.sizes.sidebarWidth)}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's take both Number.parseFloat

Comment on lines +97 to +99
onResizeStart?: (entries: Array<ResizeObserverEntry>) => void;
onResize?: (entries: Array<ResizeObserverEntry>) => void;
onResizeEnd?: (entries: Array<ResizeObserverEntry>) => void;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where entries are used?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was in the middle of refactoring and used them, then removed the usage, thought its still useful potentially since the utility is generic.

Copy link
Contributor

@johnsicili johnsicili left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1. Bindings open in middle

  1. Select an instance on the canvas
  2. Next click, open a binding
  3. See it in the middle of the page

Bindings open in unpredictable spots often. Will need to test this a lot

bindingrel.mp4

2. Style panel scroll with open dialog

  1. Open complex value
  2. Scroll style panel
  3. Click or drag dialog
  4. See jump
scrollst.mp4

Let me review again once these are fixed. These are super error prone and unpredictable IMO and we need to be careful with them. From a user perspective, they've caused my harm than help as of now.

@kof
Copy link
Member Author

kof commented Jan 5, 2025

@johnsicili seems like deployment didn't go through, you tested some buggy version

@kof
Copy link
Member Author

kof commented Jan 5, 2025

second issue is valid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dragging floating panel causes full width Pressing space in floating panel causes jump
3 participants