Closed Bug 596135 Opened 15 years ago Closed 12 years ago

Add flash-check to /start/

Categories

(Camino Graveyard :: Product Site, defect)

All
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: alqahira, Assigned: ss)

References

Details

In bug 514815 we added a check for out-of-date Flash to the welcome page (page shown on the first launch of any new version). We mentioned at the meeting (http://wiki.caminobrowser.org/Status_Meetings:2010-09-08:Log#16:10) that we thought it would be a good idea to put it on /start/, too, for everyone who doesn't change the default home page. However, to do so, we need to make some changes to conditionalize its display on the lack of an "Upgrade Camino" message (bug 514815 comment 25). Sam had some additional objections (from irc over the weekend): [9:21pm] ss: Oh, so [9:21pm] ss: I should comment. [9:21pm] ss: I'm totally okay with putting this on /welcome/ [9:21pm] ss: But I'm less okay with /start/ [9:21pm] ss: The reason being... it's annoying on /start/ to see it every time. [9:21pm] ss: And there might be some people who don't want to upgrade for whatever reason. [9:22pm] sauron: :P [9:22pm] ss: I meant to comment, but I got sidetracked with the hosting stuff. [9:22pm] sauron: "i like to use insecure things that crash my browser" [9:23pm] ss: Uh... well... I think it's more complicated than that. [9:23pm] ss: "I'm not an admin" for example. [9:23pm] ss: Or "I'm on a limited access machine" [9:23pm] sauron: does it not install locally? [9:23pm] ss: Or "I don't want to right now because I don't want to restart the browser I just restarted." [9:24pm] ss: I don't think it does, but I haven't tested. [9:24pm] ss: But even if it does, the school instances are limited access. [9:24pm] ss: They can't install anything at all. [9:24pm] sauron: then their admin #$@# well better get with the program :P [9:25pm] ss: Yes, but should we punish them because of their admin? [9:25pm] ss: Can we try /welcome/ for now, see what the stats are after a release, and then go from there? [9:25pm] sauron: we should make them annoy their admin to do his/her job :P [9:25pm] sauron: sure; the script needs work for /start/ anyway [9:26pm] ss: It's clearly been a while since you've been in school. ;) [9:26pm] sauron: so that it doesn't show both "upgrade" and "upgrade flash" [9:26pm] sauron: yes, it has :P [9:26pm] ss: Yeah [9:26pm] sauron: so this bug is just for /welcome/ [9:26pm] sauron: we'll spin a new one for /start/ and argue there once this is running [9:27pm] ss: Alright. [9:27pm] ss: Just making sure because I saw the meeting talked about /start/ [9:27pm] ss: And I admit I didn't read it in detail enough. [9:27pm] sauron: https://bugzilla.mozilla.org/show_bug.cgi?id=514815#c25 [9:28pm] ss: You think I read bugs? [9:28pm] ss: That's crazy! [9:28pm] ss: (Not sure how I missed that comment.) [9:28pm] ss: It's actually not hard to do /start/ [9:28pm] sauron: especially ones where you have (had) r? [9:29pm] ss: We'd do "if oldVersion, display oldVersionMessage, elseif oldFlashVersion display oldFlashVersionMessage, else display nothing" [9:29pm] ss: But yes, not now. [9:29pm] ss: After 2.0.5 or something.
fwiw, as it was somehow mentioned above, the 'intelligent' Flash 10.1 installer doesn't offer any option other than installing in /library/internet plugins/
My other question is, how is this any different from the "Update Camino" message we currently show on /start/ to outdated Caminos? Users in this situation (admin-controlled machines) can't update Camino, either, yet we still show them the message all the time (if /start/ remains their home page).
> ss: Can we try /welcome/ for now, see what the stats are after a > release, and then go from there? We need to turn on analytics for /start/ if we want to be able to get information about whether or not people going to /start/ would benefit from being told to update Flash. Right now we don't have any stats to look at. (Turning on analytics for /welcome/ might be nice too.)
That's now bug 597623.
I think bug 313700 is a hard blocker here; what it would cause is far worse than any of the things Sam is concerned about in comment 0.
Depends on: 313700
FWIW, we'll have a fix for bug 313700 in 2.1.3 (via bug 740620).
Given the current state of the Camino project, we won't be fixing these website bugs. Mass changing our Product Site bugs (search on "camino-website-bugs"). RESOLVED -> WONTFIX.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.