Closed
Bug 639890
Opened 13 years ago
Closed 12 years ago
Add the value attribute of elements to the list of attributes used in jum.assert messages
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
(Whiteboard: [mozmill-l10n])
http://mozmill-crowd.brasstacks.mozilla.com/#/l10n/report/f179c276497eff82ec93f78b1e39261b The duplicate access keys were backgroundColor.accesskey <http://hg.mozilla.org/l10n-central/fa/file/5e7758539fdb/browser/chrome/browser/preferences/colors.dtd#l12> and linkColor.accesskey <http://hg.mozilla.org/l10n-central/fa/file/5e7758539fdb/browser/chrome/browser/preferences/colors.dtd#l20>. Here is the message that Mozmill generated: jum.assert(false) - accessKey: پ found in string's: [id: (id is undefined), label: (label is undefined)], [id: (id is undefined), label: (label is undefined)] The undefined tokens in this message are bogus.
Comment 1•13 years ago
|
||
Well, we should add the value property as an alternative if none of the others have been specified. See: http://mxr.mozilla.org/mozilla-central/source/browser/components/preferences/colors.xul#83
Blocks: 562084
Component: Mozmill → Mozmill Tests
OS: Mac OS X → All
Product: Testing → Mozilla QA
QA Contact: mozmill → mozmill-tests
Hardware: x86 → All
Summary: Mozmill l10n test couldn't detect the names for the duplicate access keys correctly → Add the value attribute of elements to the list of attributes used in jum.assert messages
Whiteboard: [mozmill-l10n]
Comment 3•13 years ago
|
||
As you see I have moved it to Mozmill tests. It's nothing on Mozmill side.
Comment 4•12 years ago
|
||
This has been fixed a while back and short work perfectly now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•