Closed Bug 643434 Opened 13 years ago Closed 8 years ago

[Firefox] mochitest-a11y: tree/test_tabbrowser.xul reports "Error: keyClose is null / tabbrowser.xml", when manually selecting the unselected tab

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: sgautherie, Unassigned)

References

(
URL
)

Details

(Whiteboard: [auto-closed:inactivity]) 

(Noticed while working locally on bug 544170.)

1) Manually click on the unselected tab.
1r) It works, but it reports:
{
Error: keyClose is null
Source File: chrome://browser/content/tabbrowser.xml
Line: 193
}

Firefox 4.0*pre: once.
SeaMonkey 2.1*pre: none.

Fwiw, I would try to guess that this test misses a stub/mock object/feature...

NB: That's not the point of this test, but that seems odd (when working on this test).
(In reply to comment #0)
> 1) Manually click on the unselected tab.

Or use Ctrl+Tab.
Summary: [Firefox] mochitest-a11y: tree/test_tabbrowser.xul reports "Error: keyClose is null / tabbrowser.xml" → [Firefox] mochitest-a11y: tree/test_tabbrowser.xul reports "Error: keyClose is null / tabbrowser.xml", when manually selecting the unselected tab
Blocks: 643436
AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [auto-closed:inactivity]
You need to log in before you can comment on or make changes to this bug.