Skip to content

Trouble interacting with the Action Flow Editor while resolving merge conflicts #5806

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

Open
1 task
jelanijohn opened this issue May 12, 2025 · 1 comment
Open
1 task
Assignees
Labels
Bug status: confirmed Issue has been reproduced and confirmed as a bug. UI Bugs

Comments

@jelanijohn
Copy link

jelanijohn commented May 12, 2025

Can we access your project?

  • Update: At this point in time, I've already completed the merge, but I see confirm that the issue existed in general - not just with merge conflicts - so it should not be necessary.

Current Behavior

When merging two branches:

  • I open the Action Flow Editor to view the action conflict
  • attempts to interact with the editor with my mouse (click / wheel / scroll) instead affect the code view behind it.

Expected Behavior

The mouse actions' focus should be in the Action Flow Editor when it is open.

Steps to Reproduce

Merge two branches.
Be alerted of a merge conflict.
Open the Action Flow Editor.
Attempt to interact with different parts of the editor.

Reproducible from Blank

  • The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT43iP7lz6Z6vtdn4KXudcZUpBIgKVM4XYAS0sF7aCosfZT2BLMcec/RVERpXu2gdFFmIFqakWoW097mud7tVPE7BxKdRt0/zKtccz3ybHOnMZC7FJWgSHFBHtNXG0vF5LS3vR54GMlvSXgD3U2MGOuXExPqJuf3IWo4Dq/LZO4=

Visual documentation

Areti.-.FlutterFlow.-.Google.Chrome.2025-05-12.01-11-49.mp4

Environment

- FlutterFlow version: FlutterFlow v5.4.9 released May 6, 2025
- Platform: Web
- Browser name and version: Chrome Version 136.0.7103.93 (Official Build) (64-bit)
- Operating system and version affected: Windows 11

Additional Information

It is possible to get around the issue on the web platform with some css-fiddling, but it isn't ideal.

@jelanijohn jelanijohn added the status: needs triage A potential issue that has not been confirmed as a bug. label May 12, 2025
@Alezanello Alezanello self-assigned this May 12, 2025
Copy link
Collaborator

Thank you so much for bringing this issue to our attention!

I'll forward it to the engineering team for further review.

@Alezanello Alezanello removed their assignment May 12, 2025
@Alezanello Alezanello removed the status: needs triage A potential issue that has not been confirmed as a bug. label May 12, 2025
@Alezanello Alezanello added status: confirmed Issue has been reproduced and confirmed as a bug. Bug labels May 12, 2025 — with Linear
@nathankrishnan nathankrishnan added the UI Bugs label May 12, 2025 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug status: confirmed Issue has been reproduced and confirmed as a bug. UI Bugs
Projects
None yet
Development

No branches or pull requests

4 participants