Closed Bug 400858 Opened 17 years ago Closed 16 years ago

alt+d must point to location bar

Categories

(Mozilla Localizations :: sr / Serbian, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ivan.icin, Assigned: filmil)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; sr; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: 

It is used to access address bar, so it can't be used for itemes in main menu.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Confirming
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → filmil
OS: Windows XP → All
Hardware: PC → All
Depends on: 399939
Alt+d is used as ctrl+l shortcut for some compatibility (with IE). I don't see such shortcut in IE 7.
https://bugzilla.mozilla.org/show_bug.cgi?id=177508
Flags: blocking-firefox3?
Forgot to write, that D is used as shortcut key in Russian localization (top meny,  in View word).
Blocks: 399939
No longer depends on: 399939
This should be fixable just within the localization. The accesskey for the url bar is set at 

http://bonsai-l10n.mozilla.org/cvsblame.cgi?file=/l10n/sq/browser/chrome/browser/browser.dtd&rev=1.11&root=/l10n&mark=169#165

AFAICT, just set that to whatever IE does in your localization, or, if you can't figure that out, set it to "", I guess that should work.
No longer blocks: 399939
(In reply to comment #4)
> AFAICT, just set that to whatever IE does in your localization, or, if you
> can't figure that out, set it to "", I guess that should work.
"" doesn't work, I've tested.

Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #6)
> Looks like this has just been corrected in the ru locale.
> http://bonsai-l10n.mozilla.org/cvsview2.cgi?diff_mode=context&whitespace_mode=show&root=/l10n&subdir=l10n/ru/browser/chrome/browser&command=DIFF_FRAMESET&file=browser.dtd&rev2=1.82&rev1=1.81
> 
> (I wonder how it could have been tested given bug 399939?)
>
With those patch that sends 2 events. In this case it doesn't meter how many events he sends (we may call it a testcase for this bug).
But if to be sencere I fault on IRC with this bug today... But glad it's fixed. 
Changed to 'b' in l10n-sr.
OK to mark fixed?
If I can press alt+d and get my pointer in location bar, then it is OK.

BTW, this bug was also used for Russian localization, but as it is not submitted for that purpose, I think that it can be closed, no matter what is happening in that localization (they can submit new bug if necessary)
Flags: blocking-firefox3? → blocking-firefox3-
(In reply to comment #10)
> If I can press alt+d and get my pointer in location bar, then it is OK.

In RC1 bug is still present, as it doesn't work as described above.
Summary: alt+d can't be a shortcut → alt+d must point to location bar
Is there a requirement that alt+d has to bring the location bar into focus?
(In reply to comment #12)
> Is there a requirement that alt+d has to bring the location bar into focus?
Originally, this was built into the Firefox for the purpose of compatibility with IE. If that is the case (and it is), probably question should be whether there is requirement for IE to bring location bar to focus?

(In reply to comment #13)
> (In reply to comment #12)
> > Is there a requirement that alt+d has to bring the location bar into focus?
> Originally, this was built into the Firefox for the purpose of compatibility
> with IE. If that is the case (and it is), probably question should be whether
> there is requirement for IE to bring location bar to focus?
Can you please support your claim with a reference?  Also, pointing to a requirement stating that alt+d must be the shortcut to bring the location bar into focus would help.
Depends on: 441906
As a consequence of some additional reshuffling, I was able to restore alt+d, see bug 441906.  Once that patch is applied, this is OK to close.
Status: REOPENED → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 16 years ago16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.