708083 - Make PPC users more aware of Flashblock now that 2.1 has shipped

Status: RESOLVED WONTFIX

(Camino Graveyard :: Product Site, defect)

Description

[Chris Lawson (gone)]

We need to do something, DEFINITELY on the first-run page, and maybe on /start/, to alert PPC Flash users that Flashblock is now enabled by default. We're getting a fair number of PPC users wonder what "that F in a box" thing is (and why clicking on it seems to show ads so many places!) or why, e.g., the Myspace Music Player doesn't work any more in 2.1.

There's also the issue of some folks having such an old version of Flash that we already block it and thus don't show the Flashblock placeholder, which we should probably account for, too.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

We've probably missed our window of opportunity for /welcome/ at this point (1 week in), but we could maybe catch some of them on /start/ if they haven't changed their homepage.

This seems like it would have a great thing to do with bug 639122, had that been implemented :P

> There's also the issue of some folks having such an old version of Flash
> that we already block it and thus don't show the Flashblock placeholder,
> which we should probably account for, too.

I'm not sure what we can do about this case; we can't detect an installed-but-blocked version of Flash (to warn to upgrade during flash-check, for example), and I'm loath to put a Flash object on /start/ or /welcome/ just to trigger the blocked placeholder icon in these cases.

Comment 2

[philippe (part-time)]

Can we just add (for 10.4 users) a paragraph of text explaining that Flashblock is enabled, and why, and linking to the relevant doc. page ?

on /welcome/ - after the existing text
on /start/ - after the search field

Aside from this, can we add the same screenshot as under the 'Blocking Flash animations' in the docs to the Flash wiki page, or refer to it? 
http://caminobrowser.org/documentation/annoyances/#annoy_flash
http://wiki.caminobrowser.org/QA:Camino_2.1.x_and_Flash

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to philippe from comment #2)
> Can we just add (for 10.4 users) a paragraph of text explaining that
> Flashblock is enabled, and why, and linking to the relevant doc. page ?

s/10.4/PPC/

I'm thinking we might want the screenshot, too, given the confusion so far.

> on /welcome/ - after the existing text
> on /start/ - after the search field

I think I'd prefer it in the same place (after) each place.  Dunno.

> Aside from this, can we add the same screenshot as under the 'Blocking Flash
> animations' in the docs to the Flash wiki page, or refer to it? 
> http://caminobrowser.org/documentation/annoyances/#annoy_flash
> http://wiki.caminobrowser.org/QA:Camino_2.1.x_and_Flash

Done.

Comment 4

[philippe (part-time)]

layout proposal (using /welcome/):
http://dev.l-c-n.com/camino/cbo-201112/Camino.html

Comment 5

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

[7:27pm] phiw: sauron, from yesterday:
[7:27pm] phiw: 5:57pm phiw: smorgan: when you have a moment, can you have a look at bug 708083 comment 4 ?
[7:27pm] phiw: 6:00pm smorgan: Looks reasonable
[7:27pm] thebot: phiw: Bug https://bugzilla.mozilla.org/show_bug.cgi?id=708083 nor, --, ---, samuel.sidler, NEW, Make PPC users more aware of Flashblock now that 2.1 has shipped
[7:28pm] sauron: ok
[7:28pm] sauron: ss should be back soon

Comment 6

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Sam, can you weigh in on this?

Comment 7

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #1)
> > There's also the issue of some folks having such an old version of Flash
> > that we already block it and thus don't show the Flashblock placeholder,
> > which we should probably account for, too.
> 
> I'm not sure what we can do about this case; we can't detect an
> installed-but-blocked version of Flash (to warn to upgrade during
> flash-check, for example), and I'm loath to put a Flash object on /start/ or
> /welcome/ just to trigger the blocked placeholder icon in these cases.

We could also run the Flash-detection routine, and if we don't detect Flash, assume that the user is running a too-old version of Flash 10.x rather than having no Flash at all, and show an info box for installed-but-blocked, I suppose.  (And if we do detect Flash, show the Flashblock info box.)

Comment 8

[Stuart Morgan]

(In reply to Smokey Ardisson (back-ish; no bugmail - do not email) from comment #7)
> We could also run the Flash-detection routine, and if we don't detect Flash,
> assume that the user is running a too-old version of Flash 10.x rather than
> having no Flash at all, and show an info box for installed-but-blocked, I
> suppose.

This SGTM. Maybe it could be a collapsed box saying something like "You don't appear to have a working version of Flash", and if expanded it could explain that if they don't have Flash installed this in normal, but if they do it means it's blocked and needs updating.

Comment 9

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

We need to get this implemented soon.

(Also, I think the Flash placeholder image should have a title attribute that explains it's a screenshot of the real placeholder, not a functioning clickable one.)

Comment 10

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This missed 2.1.1.

Comment 11

[Samuel Sidler (:ss)]

We decided the best way to do this is through "snippets" on the homepage, right? Shouldn't be too hard to get that system setup and ultimately hook this in.

Comment 12

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Well, if "snippets" can do comment 3-4 and comment 7-8, then sure.

Comment 13

[Samuel Sidler (:ss)]

The layout won't be like comment 4 (we'll standardize on a layout), but the detection stuff shouldn't be hard since it's mostly already written. We'll just do an...

  if badFlash()
  else randomSnippet

... type statement and everything will work fine. We could probably make it a more complex if statement in the future to cover other groups we want to target.

Comment 14

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to Samuel Sidler (:ss) from comment #13)
> The layout won't be like comment 4 (we'll standardize on a layout)

Well, for this we want the layout in comment 4.

Comment 15

[Samuel Sidler (:ss)]

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.