-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
mini-browser: fix source and preview #10047
Conversation
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 can confirm the issue exists on master and is addressed by this change nicely 👍
This is working well for me, but I have one minor comment re: the open source behavior:
Perhaps that's outside the scope of this PR, but it was the main difference between our behavior and theirs that I could detect. |
38ea553
to
bcb96b8
Compare
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.
The behavior is correct and consistent. 👍
I'm still thinking of what the best behavior would be for the Resources such as:
Should likely have the sources as the primary or highest opener. |
bcb96b8
to
4ece63e
Compare
The changes should be good now if anyone is interested in another round of review 👍 The change:
|
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.
Behavior is aligned with vscode now 👍
The commit fixes issues related to `preview` and `source` in the mini-browser extension. The change: - allows users to open the source of an image if they use the command, or toolbar item. - allows users to open the preview of an image's sources if they use the command or toolbar item. The fix should also apply to all supported extension types the mini-browser declares (svg, html,...). Signed-off-by: vince-fugnitto <[email protected]> Co-authored-by: fangx <[email protected]>
The commit aligns the behavior when opening the source of a previewed (rendered) markdown to open it as `tab-after` (aligning with the behavior present in vscode). Signed-off-by: vince-fugnitto <[email protected]>
4ece63e
to
4e1501a
Compare
@colin-grant-work did you have any additional feedback for the pull-request? |
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 reiterate my approval and praise the additional steps taken to bring us into alignment with VSCode :-).
What it does
Fixes: #5110
Fixes: #5223
Closes: #5206
The change fixes the source and preview commands from the
mini-browser
to use the proper opener.The change allows us to now successfully open the source of a preview, and vice-versa which was previously not possible (master).
The commit also aligns the behavior when opening the sources from a preview to open as tab-right instead of in a new editor group similarly to the behavior present in vscode.
How to test
open source
toolbar item successfully opens the file's sources (a dialog might appear)open preview
toolbar item opens the file's previewmini-browser-fix.mp4
Review checklist
Reminder for reviewers
Signed-off-by: vince-fugnitto [email protected]
Co-authored-by: fangx [email protected]