-
Notifications
You must be signed in to change notification settings - Fork 162
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
(#209) Disable Browser First Run Wizards #522
(#209) Disable Browser First Run Wizards #522
Conversation
Opening this as draft to get it up. I noticed that both COMMITERS.md and CONTRIBUTING.md think they were modified, even though nothing but git thinks that 😂 . But it prompted me to ensure there weren't any differences with other Chocolatey ones, and noted a few things that I need to clean up about the function I've added here, so I'll get that done before marking this as ready. |
This looks useful. As per your comment, do take a look at https://github.com/chocolatey/boxstarter/blob/develop/CONTRIBUTING.md#code-standards-and-style |
👀 |
7aea2af
to
3e35a32
Compare
3e35a32
to
5398d23
Compare
5398d23
to
f71eeb1
Compare
NOTE: because of #565, it might be required to explicitly export new functions in the corresponding manifest (=> |
@corbob - in order to move forward with this, could you export |
@mwallner, absolutely. I can likely get to that later this week or weekend. |
Add function to disable browser first run wizards so that PowerShell Invoke-WebRequest can work correctly, and so that Edge doesn't pester the user to configure it.
75e1d10
to
2b17437
Compare
@mwallner I got that updated (I'm on holidays this week, so technically still the weekend I previously mentioned 😏 ) |
Description Of Changes
Add a function to disable the first run wizards of Microsoft's browsers.
Motivation and Context
Invoke-WebRequest doesn't work properly until IE is configured. Edge has a long cumbersome first run wizard that many find undesirable.
Testing
Change Types Made
Related Issue
Fixes #209
Change Checklist