Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Remove channel switching UI

VERIFIED FIXED in Firefox 5

Status

()

Firefox
General
VERIFIED FIXED
6 years ago
6 years ago

People

(Reporter: Gavin, Assigned: Gavin)

Tracking

(Depends on: 1 bug, Blocks: 1 bug)

Trunk
Firefox 7
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(firefox5+ fixed, firefox6+ fixed)

Details

(Whiteboard: [channel-switcher])

Attachments

(3 attachments, 3 obsolete attachments)

I think the channel switching UI isn't likely to be useful to enough users to outweigh the costs (confusing shortcut/app inconsistencies after channel switches, code complexity, testing burden, etc.). Jay seems to agree.

For Firefox 5, perhaps the simplest solution would be to just disable it for the release channel, as it currently is for the nightly channel.

Comment 1

6 years ago
So what's a doable target for this? Is this something we should try and get in for FF5? If we remove it, what other things do we need to have...I assume text in the UI explaining how to get on another channel, I know Limi had some ideas here.
Depends on: 658690

Comment 2

6 years ago
(In reply to comment #1)
> So what's a doable target for this? Is this something we should try and get
> in for FF5? If we remove it, what other things do we need to have...I assume
> text in the UI explaining how to get on another channel, I know Limi had
> some ideas here.

Removing the UI would be easy, but adding text probably wouldn't be possible for Firefox 5 because of localization.

Comment 3

6 years ago
I'd say we leave it as-is for Firefox 5 as it is so buried and we know it doesn't leave users broken if they do use it (only that it is ugly/doesn't match product needs in certain cases).
Whiteboard: [channel-switcher]
I dislike the idea of there being a release with channel switching ui in it and the next release not having it especially since the ui removal is very straightforward. Especially since this will set the user expectation that they can easily switch back to release when switching from Firefox 5 to Firefox 6 Aurora or Beta.

Comment 5

6 years ago
(In reply to comment #4)
> Especially since this will set the user expectation that
> they can easily switch back to release when switching from Firefox 5 to
> Firefox 6 Aurora or Beta.

I think this point about being able to get back to Firefox 5 from Aurora or Beta is something very valid to consider. We don't want users to get unintentionally stuck on a different channel because the channel switcher UI is suddenly gone.

Comment 6

6 years ago
So I just spoke to the Marketing people about this. They are ok with a solution that just involves removing the "Change" link. They are ok with not changing any text in the about box if that simplifies this. They will probably use the first run pages and such to promote the other channels. We may decide to change the about box in FF6 but we can keep it the same for FF5. 

I need to talk to Erica to make sure she is ok with this then we can move forward unless we find any other blockers to removing this for FF5. I will reply in the bug later tonight when hear back from her.

Comment 7

6 years ago
Why would we even bother changing this in Firefox 5? This totally seems like something that can wait for "normal" development and doesn't need to be shoehorned in at the end of the process, for reasons I see in comment 3.

We've already messaged it is there for 5 as well as tested the code as-is extensively...we should just keep it, stop talking about it, and yank it in the next version (my 2c anyway)
Yanking it after we've shipped it is not optimal, per comment 4/comment 5. Hiding the "Change" link now on Beta is not a risky or complicated change.

Comment 9

6 years ago
Ok. Just worried all these "trivial" changes pile up and we ping-pong between different directions, causing excessive churn. I know we are pretty set on removing it but, well, apparently we were adamant it needed to make it in as well. I'll leave that discussion to the post-mortem though.
Blocks: 660038
(In reply to comment #0)
> confusing shortcut/app inconsistencies after channel switches

I'm not sure what this means, but I guess it's about issues like bug 658690. Is this a concern for the beta channel at all? Maybe we should just exclude aurora like we exclude nightly?
Blocks: 658690
No longer depends on: 658690

Comment 11

6 years ago
(In reply to comment #2)
> Removing the UI would be easy, but adding text probably wouldn't be possible
> for Firefox 5 because of localization.

To add, Firefox 6 is string frozen, too.
(In reply to comment #10)
> I'm not sure what this means, but I guess it's about issues like bug 658690.

Yes, but also bug 649595/bug 649594.

> Is this a concern for the beta channel at all? Maybe we should just exclude
> aurora like we exclude nightly?

That would address the branding inconsistency issues (assuming we maintain the same branding for beta and release - there was talk of changing that too), but it would also reduce the utility of the UI further.
Created attachment 536113 [details] [diff] [review]
simple disable

This removes the UI entirely for beta/aurora/release channels, to match the behavior of nightly. It's the simplest patch, but perhaps isn't optimal in that it also removes the "current channel" text that informs the user of the channel that they're on. We should probably take this for Firefox 5 (and maybe 6).
Assignee: nobody → gavin.sharp
Status: NEW → ASSIGNED
Attachment #536113 - Flags: review?
Attachment #536113 - Flags: feedback?(margaret.leibovic)
I think the plan here should be:
Firefox 5 (mozilla-beta): disable the UI entirely with the "simple disable" patch
Firefox 6 (mozilla-aurora): disable the switching UI, but keep the "current channel" indicator
Firefox 7 (mozilla-central): remove all of the switching UI (and backend support in bug 660038), keep the "current channel" indicator
Attachment #536113 - Flags: review? → review?(robert.bugzilla)
(In reply to comment #12)
> > Is this a concern for the beta channel at all? Maybe we should just exclude
> > aurora like we exclude nightly?
> 
> That would address the branding inconsistency issues (assuming we maintain
> the same branding for beta and release - there was talk of changing that
> too), but it would also reduce the utility of the UI further.

Right, it would just allow end users to easily get on or off the beta channel, nothing more, nothing less. This alone seems like good utility, even though it's less than originally anticipated. Obviously beta would need to keep the release branding then.
(In reply to comment #15)
> Right, it would just allow end users to easily get on or off the beta
> channel, nothing more, nothing less. This alone seems like good utility

That utility needs to be traded off against the cost of maintaining the code, as well as the release-engineering work of generating extra updates and the QA work involved with testing them.

I am not opposed to keeping the code on trunk while we sort out what we want, but I think we've reached agreement that we should disable it entirely for Firefox 5 (and maybe 6).

Comment 17

6 years ago
Comment on attachment 536113 [details] [diff] [review]
simple disable

This looks like a safe and easy way to entirely disable the feature if that's what we decide to do.

I don't know if it's worthwhile to keep the feature to just switch between the beta and release channels, although it seems like it would be useful to keep the string that indicates the current channel, since our new version number system doesn't indicate that a build is a beta release.
Attachment #536113 - Flags: feedback?(margaret.leibovic) → feedback+

Comment 18

6 years ago
We are getting rid of it because it's fundamentally broken and we really can't find a good value add for the users to justify keeping it. It's better all around if we get rid of it for FF5..just the simpliest option is fine. We understand we publicized it but hey, lots of stuff could end up in Aurora, then get pulled. I have been over this with the product team and we have reached agreement that we should get rid of it.

Comment 19

6 years ago
We might remove it now because it's broken, but I think in the end we'll need to end up having some feature like that working some time - but we might be able to worry about it later if we have a really good strategy for advertising the channels and people getting to use them. Judging by the original target numbers, all channels except release have less than half the amount of people that should be there, and Aurora is less than 10% of the ADU we wanted to have there. We'll need some way of getting that evened out - if not the channel switcher, we need other plans. Do those exist?

Comment 20

6 years ago
That's a question for the product team. Ultimately they made the call to remove this feature and I know they are looking at ways to evangelize the channels so we can get more users. Your questions are really addressed at Jay, Mayumi and others. To be honest, I don't think the switcher in it's current form will get more people on those channels and neither did they.
For the record...

The "fundamentally broken" part is that channel switching doesn't support changing filesystem names which was just about the very first thing I got UX / product drivers to buy in to (well before the all hands) in that all three installs would identify as "Mozilla Firefox" on Windows and Firefox on Mac (this is due to Mac already being named Firefox). There were also several meetings where there were no objections to this naming and the vast majority of the implementation was completed prior to objections being raised by anyone including product marketing.

There is no additional releng work since it uses existing complete mar files for each repo. There was additional onetime releng work to teach aus to serve up these mar files.
Comment on attachment 536113 [details] [diff] [review]
simple disable

I agree with Gavin's approach in comment #14
Attachment #536113 - Flags: review?(robert.bugzilla) → review+
Comment on attachment 536113 [details] [diff] [review]
simple disable

The net effects of this patch is that the entire "You are currently on the XXX update channel. [Change]" block of the about dialog disappears (as it always has for Nightly builds).

I will investigate a slightly more involved change that maintains the text and only removes the link, for Firefox 6.
Attachment #536113 - Flags: approval-mozilla-beta?

Comment 24

6 years ago
This all sounds good to me. I also agree with Gavin's approach.

Updated

6 years ago
tracking-firefox5: --- → +

Updated

6 years ago
Attachment #536113 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Fixed on mozilla-beta for Firefox 5:
http://hg.mozilla.org/releases/mozilla-beta/rev/ed71a00e8247

I'll attach an aurora patch shortly.
status-firefox5: --- → fixed
Flags: in-testsuite-
Created attachment 536921 [details] [diff] [review]
trunk patch (remove channel switcher UI entirely)

This removes all of the channel switching functionality, but maintains the "You are currently on the *foo* update channel." text.
Attachment #536921 - Flags: review?(margaret.leibovic)
Created attachment 536927 [details] [diff] [review]
aurora patch - disable switching, leave status text
Attachment #536927 - Flags: review?(margaret.leibovic)
(In reply to comment #26)
> trunk patch (remove channel switcher UI entirely)

I suppose I could simplify this further by just moving the gChannelSwitcher.init stuff into to init() and getting rid of gChannelSwitcher - pretend I already did that!

Comment 29

6 years ago
Comment on attachment 536927 [details] [diff] [review]
aurora patch - disable switching, leave status text

Review of attachment 536927 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/base/content/aboutDialog.js
@@ +591,3 @@
>      // Only show channel selector UI on valid update channels.
>      if (this.channelValue in this.validChannels) {
> +      document.getElementById("channelChangeLink").hidden = false;

If you add back a valid channel, the channel switcher UI will still show all the hard-coded menuitems from aboutDialog.xul. Since this would make for a half-broken feature that we're planning on getting rid of anyway, why don't we just get rid of this if statement entirely?

@@ +639,5 @@
> +
> +    // Use the menuitem label if there is one for this channel, otherwise just
> +    // use the channel value.
> +    let menuItem = document.getElementById(aValue + "Menuitem");
> +    channelLabel.value = menuItem ? menuItem.label : aValue;

It's kind of odd that the only purpose of these menuitems now is to store strings, especially since you decided not to use these strings in your patch for trunk. Maybe we should just set the channel value in init() instead of calling setChannelLabel.

Comment 30

6 years ago
Comment on attachment 536921 [details] [diff] [review]
trunk patch (remove channel switcher UI entirely)

Review of attachment 536921 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/base/content/aboutDialog.js
@@ +580,2 @@
>      try {
> +      channelValue = Services.prefs.getCharPref("app.update.desiredChannel");

This isn't being set anywhere anymore, so I don't know if we should still check it. I guess as long as the back-end code remains the same a user could manually set the pref to switch channels, but is that worth exposing in our UI? It would be simpler to just look at app.update.channel.
Created attachment 536948 [details] [diff] [review]
trunk patch (remove channel switcher UI entirely)

OK, so new plan: for aurora, let's just land the trunk patch, but without the string removals.
Attachment #536921 - Attachment is obsolete: true
Attachment #536927 - Attachment is obsolete: true
Attachment #536921 - Flags: review?(margaret.leibovic)
Attachment #536927 - Flags: review?(margaret.leibovic)
Attachment #536948 - Flags: review?(margaret.leibovic)
Created attachment 536950 [details] [diff] [review]
trunk patch (remove channel switcher UI entirely)

(oops, wrong patch)
Attachment #536948 - Attachment is obsolete: true
Attachment #536948 - Flags: review?(margaret.leibovic)
Attachment #536950 - Flags: review?(margaret.leibovic)

Comment 33

6 years ago
Comment on attachment 536950 [details] [diff] [review]
trunk patch (remove channel switcher UI entirely)

Looks good to me!
Attachment #536950 - Flags: review?(margaret.leibovic) → review+
http://hg.mozilla.org/mozilla-central/rev/bb805165115d
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
status-firefox6: --- → affected
Resolution: --- → FIXED
Target Milestone: --- → Firefox 7
Created attachment 537178 [details] [diff] [review]
aurora patch (trunk patch minus string removals)
Attachment #537178 - Flags: approval-mozilla-aurora?
tracking-firefox6: --- → +

Comment 36

6 years ago
Verified fixed on Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0
Status: RESOLVED → VERIFIED

Updated

6 years ago
Attachment #537178 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
http://hg.mozilla.org/releases/mozilla-aurora/rev/3d6ab524a848
status-firefox6: affected → fixed

Updated

6 years ago
Depends on: 663704

Updated

6 years ago
Depends on: 665337
No longer depends on: 665337

Comment 38

6 years ago
It would have been nice to keep the function, but disabled/hidden by default with an option to re-enable.  If the feature really was trouble, something similar would be nice.  I switched to beta then to Aurora because of the ease of switching.  Now that I can switch back to use a few plugins, I will have to abandon the beta testing if it is not easy to switch.

Comment 39

6 years ago
Yes please include a feature to re-enable Channel Switcher.  It was really useful. Just a click to switch.  And now we'll have to download and then install different channel.

Comment 40

6 years ago
I second that this is a useful and welcome feature for beta testers.  I was wondering why I couldn't find the switch button until I found this "bug".  I think it's a mistake to remove the switch button.

Comment 41

6 years ago
I really wish it was there - I was just pushed down 6 and it broke almost all of the extensions.  Most importantly, the reddit enhancement suite has been completely broken.  No problem, I thought, I'll just change the channel back to something that I know will work.  But the button is gone.

Please bring it back.
(In reply to comment #41)
> I really wish it was there - ...
> Please bring it back.

+1

I was just saying to Wayne that now that Thunderbird is telling me the channel, why don't they implement a channel switcher? The channel switcher would be extremely useful to have for both Firefox and Thunderbird, and make it much more attractive even for technical users like me to test the trunk builds, and if anything goes wrong there, I can just switch back. That's so much easier than all the downloading stuff we've had to do so far.
(In reply to comment #42)
> ... and make
> it much more attractive even for technical users like me to test the trunk
> builds, and if anything goes wrong there, I can just switch back. That's so
> much easier than all the downloading stuff we've had to do so far.

Why not just have two (or more) builds installed that you switch between. Then you don't even have to download a new build to switch...
(and I just realised discussion like this should probably go onto the newsgroups, as commenting on a fixed bug isn't likely to get followed properly - so please follow up there).
You need to log in before you can comment on or make changes to this bug.