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

Switching Trigger maintains vertical scroll position #9717

Open
8 tasks done
mikeirvingweb opened this issue Mar 14, 2024 · 0 comments
Open
8 tasks done

Switching Trigger maintains vertical scroll position #9717

mikeirvingweb opened this issue Mar 14, 2024 · 0 comments
Labels
approved Reviewed and ready to start working on it. Will be added to the work queue in the current iteration. Area: Visual editor Backlog Backlog items - not in current milestone Type: Bug Something isn't working

Comments

@mikeirvingweb
Copy link
Contributor

Describe the bug

If you open one Trigger, scroll down, then open another, it assumes the scroll position from the previously opened one - which is unhelpful.

it should open a new Trigger with the view set at the top of the trigger.

Occurs in Web App and native wrapped apps.

Version

2.1.2

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:

  1. open a Trigger (a long one that requires vertical scrolling)
  2. scroll down
  3. then open another (another long one that requires vertical scrolling)
  4. the new trigger view assumes the scroll position from the previously opened one

Expected behavior

Screenshot 2024-03-14 at 10 45 35 Screenshot 2024-03-14 at 10 45 41 Screenshot 2024-03-14 at 10 45 48

if you open a trigger, the vertical scroll bar should be set to the top

Screenshots

Video:
https://github.com/microsoft/BotFramework-Composer/assets/79252299/503eddd3-1368-4bce-b87e-3775e417d320

@mikeirvingweb mikeirvingweb added Needs-triage A new issue that require triage Type: Bug Something isn't working labels Mar 14, 2024
@OEvgeny OEvgeny added Area: Visual editor Backlog Backlog items - not in current milestone approved Reviewed and ready to start working on it. Will be added to the work queue in the current iteration. and removed Needs-triage A new issue that require triage labels Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Reviewed and ready to start working on it. Will be added to the work queue in the current iteration. Area: Visual editor Backlog Backlog items - not in current milestone Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants