Closed
Bug 24296
Opened 26 years ago
Closed 25 years ago
Access keys not in DTDs in many cases
Categories
(Core :: Internationalization: Localization, defect, P3)
Tracking
()
M17
People
(Reporter: kairo, Assigned: matt)
References
Details
(Whiteboard: [nsbeta2+][PDT-])
I posted a message about this in n.p.m.l10n which leaded me to report this:
Access keys are not in DTDs in many cases. Sometimes there aren't any at all but
many times they've been left in the XUL files.
<Tao Cheng's answer:> Yes, this is a localization roadblock that needs to to be
removed.
If Mozilla wants to set an accesskey "v" for the menu "Ansicht" ("View" in
en-US), it leaves the menu without any access key...
<Tao Cheng's answer:> The current plan is to leave accesskey alone; Mozilla
will append the accesskey for English to the menu. For example,
"Ansicht" would become "Ansicht (Ctrl+V)".
<Yung-Fong Tang's answer:> I think this is a very common issue for Japanese /
Chinese / Korean in particulare. I remember Ray Chen (rchen) were
working w/ xp widget group (Chris Saari and David Hyatt) about this issue. What
is the update for this, ray ?
All of this is/was happening with M12 (win32) and is still happening using build
2000-01-18-08.
![]() |
Reporter | |
Updated•26 years ago
|
QA Contact: teruko → amasri
![]() |
Reporter | |
Comment 1•26 years ago
|
||
Adding QA contact to amasri@netscape.com as he wished in the thread.
Appending the accesskey character is in M13 with a minor bug which will be fixed
in M14. I will look into the issue of access keys not in DTDs.
Comment 3•26 years ago
|
||
Laura, is this a beta1 stopper?
I don't think this is beta1 stopper. Kairo, can you point out which files?
Add Fergus and Chang.
Fergus, Chang, we need to check if any access keys left in the XUL in each
components. Contact and help the developers to move them to DTD files. Thanks.
Status: NEW → ASSIGNED
![]() |
Reporter | |
Comment 6•26 years ago
|
||
The following XULs contain hardcoded accesskeys in M13:
global/.../commonDialog.xul
editor/.../editor.xul (tableMenu...)
editor/.../TextEditorAppShell.xul (insertMenu...)
(messenger/.../messenger.xul contains accesskey="" what about that?)
(navigator/.../navigator.xul contains accesskey="" what about that?)
navigator/.../navigatorOverlay.xul (menu id="menu_View"!)
pref/.../pref-advanced.xul
pref/.../pref-appearance.xul
pref/.../pref-cache.xul
pref/.../pref-colors.xul
pref/.../pref-composer.xul
pref/.../pref-cookies.xul
pref/.../pref-debug.xul
pref/.../pref-dowload.xul
pref/.../pref-fonts.xul
(pref/.../pref-navigator.xul contains accesskey="" what about that?)
pref/.../pref-proxies.xul
pref/.../pref-search.xul
pref/.../pref-smart_browsing.xul
pref/.../pref-wallet.xul
That are all XUL files containing hardcoded accesskeys. (I didn't care if the
files need to have accesskeys at all - just did a serch and looked if they're
hardcoded or entities...)
Change beta1 keyword to beta2 and Milestone to M15.
Comment 10•25 years ago
|
||
If (as it appears) this is not a blocker for the M15 stability checkpoint
branch, please push this to M16 asap.
Thanks.
Comment 12•25 years ago
|
||
setting milestone to m17
Comment 13•25 years ago
|
||
reassign it to matt.
Comment 14•25 years ago
|
||
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [PDT-] → [nsbeta2+][PDT-]
Comment 15•25 years ago
|
||
I've created a new meta-bug (40430) to track this issue. It points to all the
bugs reported as a result of this one.
Accordingly I'm closing this bug as a dupe (even though it was the
earlier of the two).
*** This bug has been marked as a duplicate of 40430 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•