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.

Sign up for GitHub

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

Jump to bottom

First letter entered in component browser stays rendered after canceling the node creation with Esc #6318

Closed
1 of 2 tasks
xvcgreg opened this issue Apr 17, 2023 · 3 comments
Closed
1 of 2 tasks

First letter entered in component browser stays rendered after canceling the node creation with Esc #6318

xvcgreg opened this issue Apr 17, 2023 · 3 comments
Assignees
@kazcw
Labels
--bug Type: bug --regression Important: regression p-high Should be completed in the next sprint s-duplicate Status: a duplicate issue
Milestone
Design Partners

Comments

@xvcgreg
Copy link

xvcgreg commented Apr 17, 2023 •
edited by sylwiabr
Loading

Discord username

No response

What type of issue is this?

Permanent – Ocurring repeatably

Is this issue blocking you from using Enso?

  • Yes, I can't use Enso because of this issue.

Is this a regression?

  • Yes, previous version of Enso did not have this issue.

What issue are you facing?

First letter entered in component browser stays rendered after canceling the node creation with Esc

2304171933_shareX.mp4

Expected behaviour

All letters disappear after the cancelation.

How we can reproduce it?

  1. press TAB
  2. start entering letters/numbers
  3. cancel node creation with ESC key

Screenshots or screencasts

No response

Enso Version

2023.4.15

Browser or standalone distribution

Standalone distribution

Browser Version or standalone distribution

standalone

Operating System

Windows

Operating System Version

11pro 22H2

Hardware you are using

12th Gen Intel(R) Core(TM) i9-12900HK / RTX3060 Laptop
@xvcgreg xvcgreg added --bug Type: bug --regression Important: regression triage labels Apr 17, 2023
@sylwiabr sylwiabr added the p-high Should be completed in the next sprint label Apr 17, 2023
@sylwiabr sylwiabr added this to the Design Partners milestone Apr 17, 2023
@kazcw
Copy link
Contributor

kazcw commented Apr 17, 2023

I'm not able to reproduce this on Linux / current develop (b700679) / backend-release=latest. I will try on a Windows machine...

@kazcw
Copy link
Contributor

kazcw commented Apr 17, 2023

I can reproduce this on Windows, 4/15 nightly. I'll look in to it.

@kazcw kazcw assigned kazcw and unassigned farmaazon Apr 17, 2023
@kazcw
Copy link
Contributor

kazcw commented Apr 18, 2023 •
edited
Loading

This is a case of the same bug as #6320 (note the same GL error in debug logs). I'll close this one, as the other description is more general

@kazcw kazcw closed this as completed Apr 18, 2023
@github-project-automation github-project-automation bot moved this from ❓New to 🟢 Accepted in Issues Board Apr 18, 2023
@farmaazon farmaazon added s-duplicate Status: a duplicate issue and removed triage labels Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kazcw kazcw

Labels
--bug Type: bug --regression Important: regression p-high Should be completed in the next sprint s-duplicate Status: a duplicate issue
Projects
Issues Board
Archived in project
Milestone
Design Partners
Development

No branches or pull requests
4 participants
@kazcw @farmaazon @sylwiabr @xvcgreg