668721 - Add 2.1-only help content for new in-product URLs related to plug-ins

Status: RESOLVED FIXED

(Camino Graveyard :: Product Site, defect)

Description

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

+++ This bug was initially created as a clone of Bug #644700 +++

We introduced several new used-in-product URLs in the plug-in blocking/disabling UI, including new sections about blocked and disabled plug-ins.

It would be nice if we could go ahead and add that content to the website in advance of beta 1 (when these features are making their wide debut), given that we're now blocking old Flash and old F4M, so that the more info links work when people do follow them to figure out why their plug-ins don't work.

However, we really shouldn't display these sections to Camino 2.0 users, because they don't apply (and, because the URLs are to anchors, we can't redirect hits to those "URLs" to the wiki or somewhere else).

Are there any methods available to us that would let on 2.1 users see the sections for these two messages? 

http://caminobrowser.org/documentation/setup/#disable_plugin
http://caminobrowser.org/documentation/setup/#blocked_plugin

Comment 1

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

Attachment: Proposed text(s)

Here's proposed text for these two sections of /setup/.  Because the most sane way to explain enabling/disabling was to refer to /hiddenprefs/, I added that and only that pref to /hiddenprefs/ as well.

For your convenience, you can also visit these sections live on stage:
http://www-stage.caminobrowser.org/documentation/setup/#disable_plugin
http://www-stage.caminobrowser.org/documentation/setup/#blocked_plugin
http://www-stage.caminobrowser.org/documentation/hiddenprefs/#DisableSpecificPlugins

Comment 2

[Stuart Morgan]

Comment on attachment 543878 [details] [diff] [review]
Proposed text(s)

Looks good to me.

Comment 3

[Samuel Sidler (:ss)]

Comment on attachment 543878 [details] [diff] [review]
Proposed text(s)

What do you think about calling the class "camino-2.1" instead of "camino-future"? I worry that camino-future isn't future-proof for later versions of Camino.

r=me either way.

Comment 4

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

(In reply to comment #3)
> What do you think about calling the class "camino-2.1" instead of
> "camino-future"? I worry that camino-future isn't future-proof for later
> versions of Camino.

Well, the idea is the CSS (and the js that twiddles it) is future-proof for all versions of Camino, so we don't have to keep changing those bits all the time.  When we move to 2.1, we just find-and-replace all the ' class="camino-future hidden"' instances, and then we can start over for Camino.next, if needed ;-)

Pushed live, with a slight tweak to disable_plugin's link text for the reference to the hidden pref.