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.

Sign up for GitHub

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

Jump to bottom

Feature Request - Startup profiles #2575

Closed
zakius opened this issue Aug 28, 2019 · 2 comments
Closed

Feature Request - Startup profiles #2575

zakius opened this issue Aug 28, 2019 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@zakius
Copy link

zakius commented Aug 28, 2019

Description of the new feature/enhancement

Add new field in settings containing profiles to use on startup. Currently present default profile should be used only for new tab functionality and as a fallback when startup profiles are not defined (for example after update).

Proposed technical implementation details (optional)

For ease of use new field should accept both string with GUID of a single profile and array of strings and if it's not present at all it should fallback to default
@zakius zakius added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 28, 2019
@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 Aug 28, 2019
@zadjii-msft
Copy link
Member

/dupe #756

That thread has a bunch more discussion on this topic, so I'll close in favor of that thread. Thanks!

@ghost
Copy link

ghost commented Aug 28, 2019

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Aug 28, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Aug 28, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zakius @zadjii-msft