This project is for pulling the network settings from a users OS settings. Specifically, on windows it means getting them from IE, just as Firefox does.
(lone): It isn't clear how we can proceed with use cases 2 and 3. UC2 could be achieved by running a connection check at every startup (as opposed to just firstrun), but I'm not sure this is something we want to do. UC3 is really problematic because the change could happen at any time, and scheduling periodic network checks seems really unreasonable, also we obviously can't rely on failures from the browser since the user could try to connect to an invalid uri.
The current thinking is to add to the network connection check a step that pulls the network settings in the case of failure to connect. If we find settings we would apply them and re-attempt a connection. Upon a second failure we would go into the current flow of manual configuration of connection settings.
(lone): I suggest that we expose the ability to import the network settings from several sources: internet explorer, mozilla, opera, and so on. Upon network failures we then try to import the settings from each of the sources, starting with the most likely (IE), until the connection succeeds. If none of the import sources yields a successful connection, we can resume to the manual proxy config.
To Resolve (with hints):
| ID | Priority | Cost | Title | Description | Engineer | Testcase |
|---|---|---|---|---|---|---|
| 18804 | P2 | 0 | Import network settings at firstrun | Songbird should automatically detect and apply network settings, such as proxy configuration, at first run. The effort should be transparent to the user. Currently we handle network connection failures in firstrun for the EULA screen (to get the language bundle) and at fetching of the addons bundle. We should not wait until this point to do the configuration check, but if we hit problems in those cases we should continue to do as we do, and show the connection dialog (knowing that partners may want to configure that experience and can overlay into the connection error dialog to do such). Initial implementation should be on Windows, but the underlying service should allow implementation on all 3 platforms (mac/linux implementations are nice-to-haves at this point) | lonedfx | 1143 |
| 19012 | P1 | 3 | Write a proxy import service | Write a service that allows importing proxy settings from several sources (IE on windows is the priority) . | lonedfx | N/A |
| 19013 | P1 | 2 | Integrate proxy import service into firstrun | At firstrun, if a network connection fails, songbird should try to import the proxy settings from each of the available sources until a succesful connection is established, or until there are no more proxy import sources at which point the existing manual network dialog should appear (note that we may want to disable the manual configuration dialog for some builds, this is part of a future task). The process should be transparent to the user. | lonedfx | 1143, 4136, 4141, 4145 |
Top level things to consider across all stories/tasks.
| Images 0 | ||
|---|---|---|
| No images to display in the gallery. |