Confirmed users
2,492
edits
Firefox/Features/Installers: Difference between revisions
Jump to navigation
Jump to search
→Problems
| Line 126: | Line 126: | ||
** '''Windows:''' The Firefox logo will change to the Firefox logo but the shortcuts will all show Aurora as the name. | ** '''Windows:''' The Firefox logo will change to the Firefox logo but the shortcuts will all show Aurora as the name. | ||
===Problems=== | ===Problems/Issues=== | ||
There are a number of issues | There are a number of issues here to discuss. | ||
1. If a user were to come along install Aurora from the download page, then use the channel switcher to switch to Beta, the logo changes to the Firefox icon of the app changes but the text will forever show Aurora. | 1. If a user were to come along install Aurora from the download page, then use the channel switcher to switch to Beta, on Mac the logo changes to the Firefox icon of the app changes but the text will forever show Aurora. On Windows, we get the same behavior but all shortcuts will also show Aurora as the name although it's not. | ||
* | * There is a bug here where the logo doesn't always change. | ||
* Based on today's implementation, if the user started out with a Beta or Release build and channel switched to Aurora, the icon would change but the text would say Firefox in both scenarios. Not as confusing as going from Aurora->Release but not great. | * Based on today's implementation, if the user started out with a Beta or Release build and channel switched to Aurora, the icon would change but the text would say Firefox in both scenarios. Not as confusing as going from Aurora->Release but not great. | ||
2. | 2. There are a few options to solve the above problem... | ||
* We | * a) All channels could be installed as Firefox. If the app name were Firefox.app for everything and we wouldn't end up in a situation where the text, short cuts or app name was out of sync with the thing we are running. | ||
* | ** On Mac: If all channels were installed as Firefox.app then installing with normal dmg method to Applications will overwrite existing installations (Aurora, Beta, Release). | ||
** On Windows: If all channels were installed as Firefox.app then the standard install method will overwrite the existing install. This is not problematic since the advanced install allows the user to select the install directory. We would also need to provide an option to name the shortcuts during an advanced install so the shortcut doesn't overwrite existing shortcuts. Not a trivial amount of work. | |||
* b) We could try and change the text to be consistent with the thing we are running ie: change from Aurora to Firefox. | |||
** On Mac: We run into 2 problems. We can't actually change the Aurora.app name to Firefox.app IF there is another Firefox.app in the Applications directory, which is probably likely. We would also NOT be able to change this for any secondary users since we do not have access to their doc configuration files. | |||
* c) We could do nothing. This basically means that for the exact use case where users start out with the Aurora channel and channel switch, they end up in a very confusing situation. This would happen on both Windows and Mac but may be a very small set of users and largely an edge case. In the more likely scenario, they would start from Beta and Release, they would simply see everything as Firefox. | |||
3. Currently we use the same app name and logo between Beta and Release. This decision was made for several reasons. Firstly, it minimizes release risks. We have an option NOT to rebuild the app. AV or other 3rd parties may look for "Firefox" versus "Firefox Beta" or the reversed. Having different app names can invalidate a lot of testing depending on the way 3rd party vendors interact with Firefox. Any changes between beta and release have the opportunity to cause regressions or interact differently with 3rd parties. Because going to release is an atomic operation, there is no time to really test these and changes have the potential to invalidate all the testing we have already done (as that testing was under different variables). the consequences here are that we can brand the start-up page AND the about box but using the app name and logo, we would not be able to do. | 3. Currently we use the same app name and logo between Beta and Release. This decision was made for several reasons. Firstly, it minimizes release risks. We have an option NOT to rebuild the app. AV or other 3rd parties may look for "Firefox" versus "Firefox Beta" or the reversed. Having different app names can invalidate a lot of testing depending on the way 3rd party vendors interact with Firefox. Any changes between beta and release have the opportunity to cause regressions or interact differently with 3rd parties. Because going to release is an atomic operation, there is no time to really test these and changes have the potential to invalidate all the testing we have already done (as that testing was under different variables). the consequences here are that we can brand the start-up page AND the about box but using the app name and logo, we would not be able to do. | ||