Repository navigation
fix(v3): handle the SetFullscreenButtonEnabled runtime call - #5976
leaanthony merged 3 commits into
Conversation
Signed-off-by: Artem Muterko <artem@sopho.tech>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
WalkthroughThe window message processor now handles ChangesFullscreen button handling
Estimated code review effort: 2 (Simple) | ~10 minutes Mergeability Score: ⚪ Minimal · up to This localized fix enables the fullscreen-button runtime call and adds regression coverage; no actionable merge-blocking risk remains beyond normal checks and review. Possibly related PRs
Suggested labels: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Submitted through the wrong connector identity during automated validation; superseded by taliesin-ai review.
|
Nice catch! Thank you 🙏 |
…etFullscreenButtonEnabled runtime call
…#5976) Signed-off-by: Artem Muterko <artem@sopho.tech> Co-authored-by: Lea Anthony <lea.anthony@gmail.com>
…le the SetFullscreenButtonEnabled runtime call
…#5976) Signed-off-by: Artem Muterko <artem@sopho.tech> Co-authored-by: Lea Anthony <lea.anthony@gmail.com>
…le the SetFullscreenButtonEnabled runtime call
Description
The JS runtime ships
Window.SetFullscreenButtonEnabled(method 28) butprocessWindowMethodhas no case for it, so the call always rejects withUnknown method 28.Type of change
How Has This Been Tested?
New unit test that fails before the fix and passes after; package suite green.
Test Configuration
Checklist:
Summary by CodeRabbit
New Features
Bug Fixes
Tests