466967 - Opening a stream URL produces Empty Tab with keyboard "dead". Ctrl-W, Ctrl-T, Ctrl-Tab, Alt-D, Alt-F, [F1] etc. do not work.

Status: RESOLVED INCOMPLETE

(Firefox :: Keyboard Navigation, defect)

Description

[Peter B]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 ImageShackToolbar/5.0.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 ImageShackToolbar/5.0.0

A stream URL opened in FF3 is usually passed on the the appropriate handler-application, e.g. Windows Media Player. If it was opened in a new Tab, this Tab remains empty (OK). But the new Tab does not respond to keyboard actions (not OK).

Reproducible: Always

Steps to Reproduce:
1. Create a webpage containing this piece of HTML (just an example):
   <a target="_blank" href="http://81.173.4.20/radio538">Radio 538 stream</a>
2. Make sure that FF3 is configured for opening a Tab when HTML contains target="_blank".
3. Open this webpage in FF3.
4. Click the link.
5. A new Tab opens, and the URL (or Mime Type) causes Windows Media Player to take over. The new Tab shows no content.
6. Audio playback starts in WMP after a few seconds.
7. Go back to FF3, make sure the new empty Tab is still displaying.
8. Try closing it using Ctrl-W... does not work.
8. Try opening a new Tab using Ctrl-T... does not work.
9. Try Tabbing away using Ctrl-Tab or Ctrl-Shift-Tab... does not work.
10. Try opening the File menu using Alt-F... does not work.
10. Try activating the Address bar using Alt-D... does not work.
12. Try opening Help using F1... does not work.
13. Click any other (normal) Tab. Cycle through Tabs be keeping Ctrl-Tab pressed. Cycling will stop as soon as dead tab is reached.
Actual Results:  
Keyboard is completely dead in an empty Tab created in this way.

Expected Results:  
Keyboard should function. Empty Tabs created in this way should behave the same as empty Tabs created using Ctrl-T.

Comment 1

[Tyler Downer [He/Him]]

This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.