Repository navigation
Fix CI setup and context-menu browser failure - #15
Open
ThePyProgrammer wants to merge 3 commits into
Open
ThePyProgrammer wants to merge 3 commits into
ThePyProgrammer wants to merge 3 commits into
Conversation
ThePyProgrammer
marked this pull request as ready for review
November 5, 2026 04:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix frontend installation by aligning KaTeX with its Tiptap peer dependency and running CI on Node 26. Use the matching prebuilt Playwright image to avoid the browser installer that hung for six hours, with a 15-minute job limit and shorter step/test limits.
Keep context submenus open while the pointer crosses neighboring rows to reach them, fixing the browser test failure exposed once installation completed. Adds a regression test and updates hover assertions for the delay.
Validation: clean npm install, frontend build, 405 frontend tests, and five consecutive runs of the affected browser test passed locally. GitHub CI verification is in progress.