Closed Bug 956661 Opened 12 years ago Closed 10 years ago

[ku] Test failure "A new window has been opened" in /testPrivateBrowsing/testOpenClosePBKeyboardShortcut.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

x86
Linux
defect
Not set
normal

Tracking

(firefox26 affected, firefox27 affected, firefox28 affected)

RESOLVED WONTFIX
Tracking Status
firefox26 --- affected
firefox27 --- affected
firefox28 --- affected

People

(Reporter: mario.garbi, Unassigned)

References

()

Details

(Whiteboard: [mozmill-test-failure])

Noticed this while investigating another issue with ku locale on linux. It seems that the issue was also caught by Andreea in Bug 905963 Comment 2. http://mozmill-crowd.blargon7.com/#/functional/report/40742e0746fd767e6d2fd586598d2307
According to Francesco's comment 6 in Bug 905963 this is not something that can or will be fixed, but it is something we might encounter while/if testing 'ku'.
What's the problem here and what makes it different to bug 905963?
Flags: needinfo?(mario.garbi)
It's the same issue discovered by Andreea in bug 905963, the difference is that this bug is logged specifically for ku as it was fixed for ga-IE but not for ku. We could close it as invalid or WONT FIX, I figured we should have a bug logged for this locale too in case someone wants to report a failure as bug 905963 is closed as RESOLVED FIXED.
Flags: needinfo?(mario.garbi)
(In reply to mario garbi from comment #3) > We could close it as invalid or WONT FIX, I figured we should have a bug > logged for this locale too in case someone wants to report a failure as bug > 905963 is closed as RESOLVED FIXED. So why no bug has been filed yet and in the future please choose a better summary which also includes the locale. That will stop any confusion. I assume this bug is also present for beta and release?
Summary: Test failure "A new window has been opened" in /testPrivateBrowsing/testOpenClosePBKeyboardShortcut.js → [ku] Test failure "A new window has been opened" in /testPrivateBrowsing/testOpenClosePBKeyboardShortcut.js
And where is the localization bug? It has still not been filed, right?
I haven't filled a localization bug due to the information from Francesco in comment 6 of Bug 905963: "...ku is not working at all (last sign-off is for Firefox 10)..." I can fill in a localization bug, I just figured it wouldn't do us any good if there isn't a chance to get this fixed.
That only means that no-one is working on this localization at the moment. Do you know how it will look like in a couple of months from now on? To ensure that brokenness gets fixed, you always have to file bugs. Otherwise issues are forgotten. Lets be more pro-active and not conservative.
Depends on: 957106
We don't have Kurdish builds anytime longer. So there is no need to keep this bug open.
Status: NEW → RESOLVED
Closed: 10 years ago
Depends on: 1103991
Resolution: --- → WONTFIX
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.