Add the value attribute of elements to the list of attributes used in jum.assert messages

RESOLVED WORKSFORME

Status

Mozilla QA
Mozmill Tests
RESOLVED WORKSFORME
7 years ago
5 years ago

People

(Reporter: Away for a while, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [mozmill-l10n])

(Reporter)

Description

7 years ago
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.
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 2

7 years ago
henrik,
Is this a test bug or is this a framework bug?

Thanks.
As you see I have moved it to Mozmill tests. It's nothing on Mozmill side.
This has been fixed a while back and short work perfectly now.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.