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)

x86
Windows 98
defect

Tracking

()

VERIFIED DUPLICATE of bug 40430

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.
QA Contact: teruko → amasri
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.
Keywords: beta1
Target Milestone: M14
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
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...)
It would be nice to have, but not essential. PDT-.
Whiteboard: [PDT-]
Change beta1 keyword to beta2 and Milestone to M15.
Keywords: beta1beta2
Target Milestone: M14 → M15
This bug blocks bug #30456.
Blocks: 30456
If (as it appears) this is not a blocker for the M15 stability checkpoint branch, please push this to M16 asap. Thanks.
moving to m16
Blocks: 12394
Target Milestone: M15 → M17
setting milestone to m17
Keywords: nsbeta2
reassign it to matt.
Assignee: rchen → matt
Status: ASSIGNED → NEW
Keywords: beta2
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [PDT-] → [nsbeta2+][PDT-]
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
verifying as a dupe
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.