Open site previews in VS Code integrated browser#1621
Open
priyanshu92 wants to merge 1 commit into
Open
Conversation
Open Power Pages site previews in VS Code's integrated browser when the command is available, and keep the existing Edge Tools flow as the fallback for older builds. Copilot-Session: e313faed-11b2-4875-88ea-6cb213b7f097
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
1 participant
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.
Power Pages previews should use VS Code's integrated browser on newer VS Code builds, so users can keep the preview inside the editor without depending on Edge Tools first.
This change routes Preview Site through
workbench.action.browser.openwhen that command is available. Older VS Code builds keep the current Edge Tools behavior, including the existing install prompt when Edge Tools is missing. I avoided Simple Browser as a fallback because it does not render Power Pages sites reliably.I also updated the Preview Site tests to cover integrated browser launch, Edge Tools fallback, and the missing-Edge-Tools prompt. The desktop integration test runner now uses a short temp user-data directory so macOS socket path limits do not break test runs from long worktree paths.
Validation:
npm run compile-testsnpm run buildnpm run test-desktop-int