-
Notifications
You must be signed in to change notification settings - Fork 376
fix: prevent splitter overlay from loading in focus mode #5670
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
base: main
Are you sure you want to change the base?
Conversation
🎭 Playwright Test Results❌ Some tests failed ⏰ Completed at: 09/22/2025, 07:47:51 PM UTC 📈 Summary
📊 Test Reports by Browser
🎉 Click on the links above to view detailed test results for each browser configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the minimap/controls stuff will be a follow-up?
Let me confirm the expected behaviour internally and revert
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given the massive number of regenerated snapshots, I wonder if it is feasible to apply my suggestions (assuming you agree that they are valid) then open a new PR (given it's only 5 or so lines changes)? WDYT?
/> | ||
</template> | ||
</LiteGraphCanvasSplitterOverlay> | ||
<GraphCanvasMenu v-if="!betaMenuEnabled && canvasMenuEnabled" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we accidentally dropped the !betaMenuEnabled
check here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so I dropped it because we had 2 Graphcanvas components and thebetaMenuEnabled check was logically irrelevant
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 GraphCanvasMenu components? Apologies for not understanding
</LiteGraphCanvasSplitterOverlay> | ||
<GraphCanvasMenu v-if="!betaMenuEnabled && canvasMenuEnabled" /> | ||
<GraphCanvasMenu v-if="canvasMenuEnabled" class="pointer-events-auto" /> | ||
<MiniMap v-if="comfyAppReady && minimapEnabled" class="pointer-events-auto" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similar to above, the MiniMap
was previously inside of a parent that only rendered when !betaMenuEnabled
, so now we may need to move that condition directly into the v-if
here.
There seems to be merge conflicts. |
This pull request updates the display logic for the
LiteGraphCanvasSplitterOverlay
component inGraphCanvas.vue
. The change ensures that the splitter overlay is only shown when the application is ready, the beta menu is enabled, and the workspace is not in focus mode.Conditional rendering improvement:
LiteGraphCanvasSplitterOverlay
component is now hidden whenworkspaceStore.focusMode
is active, preventing it from being displayed in focus mode. (src/components/graph/GraphCanvas.vue
)Fixes Bug: "Focus Mode(F)" Front-end performance is abnormal #5658
Screen.Recording.2025-09-19.at.21.41.46.mov
┆Issue is synchronized with this Notion page by Unito