Same accesskey reference for Tools - Web search and context menus Search the web for ..




14 years ago
13 years ago


(Reporter: ville.pohjanheimo, Unassigned)


Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8b2) Gecko/20050529 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8b2) Gecko/20050529 Firefox/1.0+

The  Tools -> Web Search  item and the context menus  Web Search for 'selected
text'  items both reference the same accesskey from browser.dtd which makes
localizing difficult as not all languages have similar 'optimal' ways of saying
Web Search for.. and Web Search (bar).

Case in point being Finnish where  Web Search  is sensible to translate as 
Hakupalkki  (with the current behaviour of the menu selection) and  Web Search
for '...'  is translated as  Etsi verkosta "... ". Having a single accesskey for
these two strings is no-good.

Of course the exact choise of words here (for Finnish at least) is debatable,
but it's not reasonable to use the same accesskey for different strings.

Reproducible: Always

Steps to Reproduce:

Expected Results:  
Unique accesskeys for unique strings (and preferable for unique DTD or
properties keys too).
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.