Skip to content
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

Integrated Browser #6536

Closed
gkgaurav31 opened this issue Jun 16, 2020 · 6 comments
Closed

Integrated Browser #6536

gkgaurav31 opened this issue Jun 16, 2020 · 6 comments
Labels
Area-Extensibility A feature that would ideally be fulfilled by us having an extension model. Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason.

Comments

@gkgaurav31
Copy link

It would be really helpful if we can integrate any browser with the Terminal (in a different tab maybe). That will avoid having to go to another Window to test the application (for example).

@gkgaurav31 gkgaurav31 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 16, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 16, 2020
@zadjii-msft
Copy link
Member

Oh man, I tried doing this about a year ago. This is what started #1080. As it turn out, we can't use a WebView with the system XAML Islands, so we actually can't do anything like this until WinUI 3.0 lands, and we can use that implementation of XAML Islands.

It's a perfectly great idea, so I'm gonna throw it in the #4000 pile.

@zadjii-msft zadjii-msft added Area-Extensibility A feature that would ideally be fulfilled by us having an extension model. Product-Terminal The new Windows Terminal. labels Jun 16, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 16, 2020
@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Jun 16, 2020
@DHowett
Copy link
Member

DHowett commented Jun 16, 2020

I'm inclined to NAK this one, actually. We will never be able to host a browser, even as an extension, that is going to be viable for use as a browser with all the right navigation and UI/UX affordances. I don't even think that it's right for an extension author to go down this road, and I don't think we should encourage that by leaving this issue open as even a suggestion.

Browsers serve an incredibly specific purpose, and that purpose overlaps not even a little with that of a terminal emulator.

@WSLUser
Copy link
Contributor

WSLUser commented Jun 16, 2020

I think what's really desired here is simply the ability to combine browser tabs with Terminal tabs like was originally happening with Sets. An extension that supported this would be ideal. If this occurred, the use-case above (a very common one at that) would simply be a matter of switching the tab instead of window. The keybinding for switching tabs would ideally also be supported in this scenario, though that should be left to the browser to decide, not Terminal (which I believe just follows normal Windows conventions by default). Note: This may be easier to implement as a browser extension, assuming an API existed in Terminal that could be utilized.

@DHowett
Copy link
Member

DHowett commented Jun 16, 2020

But, like... Terminal is one component of a development environment. It's an important one, yes, but it's not going to grow to encompass typescript compilation or project workboard management or team chat or any number of other things that there are very good dedicated tools to do. Browsers are incredibly diverse and divisive, and we're better served by letting users choose (and mixing and matching) the components of their development environments than by trying to be the be-all end-all tool.

Even VSCode, which does purport to handle a bunch of those things, doesn't seem to have an ordained browser preview extension -- and it's literally a browser with a text editor inside it!

@DHowett
Copy link
Member

DHowett commented Jun 16, 2020

So, I'm gonna close this but I'm not going to lock it. Let's continue the discussion.

My word is not, and cannot ever be, truly final 😄

@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jun 16, 2020
@DHowett DHowett closed this as completed Jun 16, 2020
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Jun 16, 2020
@DHowett DHowett added the Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason. label Jun 16, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 16, 2020
@oising
Copy link
Collaborator

oising commented Jun 16, 2020

Zawinski's law of software envelopment: Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Extensibility A feature that would ideally be fulfilled by us having an extension model. Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal. Resolution-Won't-Fix We're just really obstinate about this. There's probably a good reason.
Projects
None yet
Development

No branches or pull requests

5 participants