273416 - Not enough info for Image Manager, Managing Image and Image permissions

Status: NEW

(SeaMonkey :: Help Documentation, defect)

Description

[David E. Ross]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20040910

I wanted to make a manual entry into the list of block image sites.  I
discovered there is no Help information.  

Reproducible: Always
Steps to Reproduce:
1.  On the menu bar, select [Tools > Image Manager > Manage Image Permissions].  
2.  On the resulting Image Manager window, select the Help button.  
3.  On the resulting Mozilla Help window, select Search, enter "Image Manager",
and select the Search button.  

Actual Results:  
At step 2, I got the "Welcome to Mozilla Help" and not help specific to Image
Manager.  

At step 3, the search result was "[no matching items found]".  

Expected Results:  
Information on how to create an entry in the list of image sources manually. 
Specifically, I wanted to see if wildcards were allowed because I can't remember
if that capability was implemented yet.

Comment 1

[Gérard Talbot]

Reporter, there is an Using Privacy Features/Managing Images section in the help
contents tab and a Tools/Options.../Web Features/Load images help content in
Firefox. I agree with you that both of these help contents are a bit meager in
content, details and useful info (like wildcards). And there should be an Image
Manager help section linked to the same Managing Images section in Mozilla.

Could you provide here what textual content would need to be added to make such
respective help sections more complete, useful? and where in the help
contents...? in the Expected results, for Mozilla. 

Personnally, I think that when one clicks the Help button in the Image Manager
window (step 2), then he should be brought accordingly to the correct, precise
spot in the Help contents section where Image manager or Image permissions or
Managing Images help section is discussed, explained. The user should not have
to search (your step 3).

Mozilla 1.8a6 build 2004120706 and Firefox 1.0 final release rv: 1.7.5 build
20041107 under XP Pro SP2 here.

Comment 2

[David E. Ross]

First of all, the capability to use wildcards is not yet implemented.  It's bug
69758 (Unconfirmed).  A capability for regular expressions is in bug 78104
(Assigned).  Both of these would affect the Help information.  To avoid fixing
this bug and then redoing the fix for those other bugs, perhaps they should
block this one.  I'll leave that decision to the experts.  

I outline the necessary Help information here.  However, the actual text should
be deferred until we know if my suggestion on blocking is followed.  

All new and revised Help information relative to this bug belongs under "Using
Privacy Features" > "Managing Images" (Contents headings).  

The Contents heading "Using Privacy Features" should instead be "Privacy &
Security Preferences" to match the heading in the actual Help text.  

Under "Managing Images", the text section heading "Privacy & Security
Preferences - Images" should instead be "Image Preferences" to match the listing
in Contents.  

Under "Privacy & Security Preferences - Images" (to be "Image Preferences"), the
Manage Image Permission button needs at least a brief description with a
reference to new Help information -- "Image Manager" -- for the Image Manager
window.  

A new section "Image Manager" is needed to describe the use of the Image Manager
window, under "Managing Images" in parallel with "Image Preferences".  This
section should describe the Remove Site and Remove All Sites buttons and how to
create a new entry (using the input area near the top of the window and the
Block and Allow buttons).  The Help button on the Image Manager window should go
directly to this new entry.  

For current capabilities, a new entry is only a domain; this needs to be
described in the new section.  With implementations to bug 69758 and bug 78104,
this would have to describe how to form an entry, including what limitations are
imposed on the use of wildcards and regular expressions and even a brief
indication of what happens with a malformed entry.  

Merely saying "wildcard" or "regular expression" for forming entries in Image
Manager after bug 69758 and bug 78104 are implemented would be insufficient for
the intended end-users, who likely do not know those terms.  Since other
capabilities use (or will use) wildcards and regular expression (the latter
generally familiar only to those experienced in using Unix), these should be
detailed under "Glossary" and not under "Using Privacy Features".  

(Slightly off-topic:  While preparing this comment, I noticed the large extent
to which headings in the Contents fail to match headings in the actual Help
text.  This is very confusing.  I will submit a separate bug report on this.  In
the meantime, I would hope fixing this bug includes the heading changes
indicated above.)  

Comment 3

[Gérard Talbot]

> To avoid fixing this bug and then redoing the fix for those other bugs,
perhaps > they should block this one.

Setting dependency under bug 78104

> headings in the Contents fail to match headings in the actual Help text.  This 
> is very confusing.

I agree. Vocabulary, expressions should be more consistent from the Preferences
dialog to the Help contents. But things are less confusing if Help buttons in
dialog bring the user to the correct location in the Help contents: no searching
either.

Comment 4

[Stefan [:stefanh]]

(In reply to comment #3)
> > To avoid fixing this bug and then redoing the fix for those other bugs,
> perhaps > they should block this one.
> 
> Setting dependency under bug 78104

Considering that bug 78104 was opened 2001-04-29 and is a RFE, it might take a
while until it's fixed... Someone could actually fix what's possible and then
file a new bug dependent of 78104.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[David E. Ross]

With a dial-up connection, I have not been downloading SeaMonkey 2.x nightlies.  I just now confirmed this is still a problem with SeaMonkey 1.1.16.  Unless significant changes are being made to the Help text for SeaMonkey, this will likely remain a problem with SeaMonkey 2.x.

Comment 7

[Ian Neal]

Confirming that documentation is still needed on how to use the Exceptions - Images dialog.