Closed Bug 905988 Opened 12 years ago Closed 12 years ago

[ff] Test failure "Search bar has the focus" in /testSearch/testSearchViaShortcut.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox24 fixed, firefox25 fixed, firefox26 fixed, firefox27 unaffected, firefox-esr17 unaffected)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox24 --- fixed
firefox25 --- fixed
firefox26 --- fixed
firefox27 --- unaffected
firefox-esr17 --- unaffected

People

(Reporter: cosmin-malutan, Assigned: AndreeaMatei)

References

(
URL
)

Details

(Whiteboard: [mozmill-test-failure])

Heapened today on Windows 7 with Release ff http://mozmill-release.blargon7.com/#/functional/report/b7ef1fb3d9703aeaf2c46e07d2e5801f It reproduces locally with this localization, it doesn't with others, I didn't checked Nightly and Aurora yet.
I could imagine that this is a problem with the access key under this locale. Please check that. If it is locale specific please note this in the future in the summary.
Summary: Test failure "Search bar has the focus" in /testSearch/testSearchViaShortcut.js → [ff] Test failure "Search bar has the focus" in /testSearch/testSearchViaShortcut.js
I'll look into this.
Assignee: nobody → andreea.matei
URL: http://mozmill-release.blargon7.com/#... → http://mozmill-release.blargon7.com/#...
Whiteboard: [mozmill-test-failure]
Here's the responsible dtd: http://mxr.mozilla.org/l10n-mozilla-beta/source/ff/browser/chrome/browser/browser.dtd#369 Command key + "t" on windows' [ff] locale will open a new tab. There should be "k" like the rest of the locales and like the description says. The second commandkey2 with "e" will focus the search bar. Will file a bug in localization.
Status: NEW → ASSIGNED
status-firefox24: ? → affected
status-firefox25: ? → affected
Depends on: 907722
This is now fixed for beta as well: http://mxr.mozilla.org/l10n-mozilla-beta/source/ff/browser/chrome/browser/browser.dtd#369 Although I don't see the change on mxr for release, I've tested it and it's fixed there as well. Leaving a few more days open to be sure. http://mxr.mozilla.org/l10n-mozilla-release/source/ff/browser/chrome/browser/browser.dtd#359
status-firefox24: affected → fixed
OS: Linux → All
Hardware: x86_64 → All
We'll need to wait for the new release here, Windows still reproduces the issue.
This was fixed in release as well now. We're done here!
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
status-firefox23: affected → ---
status-firefox26: unaffected → fixed
status-firefox27: --- → unaffected
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.