471730 - Create a dynamic content block for upcoming features

Status: RESOLVED WONTFIX

(support.mozilla.org :: Knowledge Base Articles, task)

Description

[Kevin Brosnan]

Both the comments in Private Browsing are "The Tools menu does not have private browsing" which means that they are using Firefox 3 or earlier. There needs to be a prominent message that informs users that this feature can only be found in Firefox 3.1.

Comment 1

[Chris Ilias [:cilias]]

There are at least 4 new articles for 3.1, and I think we would be better off using a custom message in each article, pointing them to related articles that the user may be looking for. (e.g. In "Private Browsing", point them to "Clearing private data", etc.. For "This Connection is Untrusted", point them to "Secure Connection Failed".)

Comment 2

[Kevin Brosnan]

I'm not too picky about the notification method. I thought a dynamic content block would work well because it could be removed quickly when Firefox 3.1 is released.

Comment 3

[David Tenser [:djst]]

What Kevin means here (I think) is a message that will appear for people not running 3.1 that clearly says that the article describes a feature that is only available in 3.1. For that, a dynamic content block seems like the best solution. This would also have the (good!) side-effect of having the SHOWFOR options visible, since we can make sure the message only appears for 2.0 and 3.0 users.

Chris, could you take this?

Comment 4

[Chris Ilias [:cilias]]

I understand that, but I'm saying a dynamic content block is not the best solution, because it only applies to a handful of articles, and it is more helpful to have a custom message for each of those articles. For instance, if you go to <http://support.mozilla.com/kb/The+bookmarks+and+history+system+will+not+be+functional?bl=n> and display content for Firefox 2, you get a message directing you to the Lost bookmarks article and Basic troubleshooting.

Comment 5

[David Tenser [:djst]]

OK. Since the number of articles affected is small, that sounds fine. WONTFIXing this bug, but we need to add these custom messages to e.g. Private Browsing. Chris, can you take care of that instead (no bug filing needed)? :)