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

[Improvement] improve zoom-in behavior in console pipeline builder #510

Closed
1 task done
xiaofei-du opened this issue Feb 24, 2024 · 2 comments
Closed
1 task done
Assignees

Comments

@xiaofei-du
Copy link
Member

xiaofei-du commented Feb 24, 2024

Is There an Existing Issue for This?

  • I have searched the existing issues

Where are you aiming to make improvements?

Console

Is your Proposal Related to a Problem?

Upon zooming in on certain areas within the console pipeline builder, the entire page enlarges, affecting the top-right navigation, sometimes causing it to disappear. Through experimentation, I've observed that this issue occurs when zooming in on specific component areas, such as

  1. the end operator field under "See Result" mode and
  2. the output section of all components.
CleanShot.2024-02-24.at.00.36.02.mp4

Describe Your Proposed Improvement

I propose investigating the root cause of this behavior. Why do only certain fields exhibit this undesired enlargement effect?

Highlight the Benefits

Identifying and addressing the cause of this issue will lead to improvements in the affected fields, enhancing the overall user experience.

Anything Else?

No response

Copy link

linear bot commented Feb 24, 2024

@xiaofei-du xiaofei-du changed the title [Improvement] improve zoom-in on console pipeline builder [Improvement] improve zoom-in behavior in console pipeline builder Feb 24, 2024
@pinglin pinglin transferred this issue from instill-ai/community May 19, 2024
@felixcorleone
Copy link

@xiaofei-du Given that this issue hasn't been updated for a long time and we now have new product plans, I will close this request and the corresponding GitHub issue. If the need arises again, please update the latest requirements and status according to the current situation.

@felixcorleone felixcorleone closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2024
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

No branches or pull requests

3 participants