If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Using two pages with text entry fields; switching to another tab the text is still written into the old tab

NEW
Unassigned

Status

()

Core
DOM: Events
--
minor
8 years ago
8 years ago

People

(Reporter: mail.d, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.12) Gecko/2009070611 Firefox/3.0.12 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.12) Gecko/2009070611 Firefox/3.0.12 (.NET CLR 3.5.30729)

After initial search (or general text entry) on one site then changing the tab and then switching away and back to FF the subsequent seach item is filled in the old page's text field. Means: The text field on the actual tab isn't detected, the old in the background still active one is used instead. It works, of course, if one clicks into the text field. But if you don't FF doesn't realize that it is on the wrong tab.

Reproducible: Always

Steps to Reproduce:
1.open http://dict.tu-chemnitz.de in tab 1
2.open www.dict.cc in tab 2
3.enter seach item in tab 1
4.switch to tab 2 without clicking into the search box
5.alt+tab to word and back to FF
6.type without clicking into the search field of tab2
 ->text will be entered into tab 1 although tab 2 is on top 

Works with different page combinations


Expected Results:  
Better was, if ff realized, that the tab has changed

word 2007 sp2

Updated

8 years ago
Duplicate of this bug: 506579
Reproducible with 3.0.12 and 3.5.1 on Windows 7:
* Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.12) Gecko/2009070611 Firefox/3.0.12 (.NET CLR 3.5.30729)
* Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)

This issue was mentioned in non-duplicate bug 226386 comment 4

It seems like focus is put on a text field in background tab #1 if focus() is called onload and page #1 finishes loading while tab #2 is in the foreground.  Text typed on tab 2 will go only into the focused field on page #1.

Timing is a factor in the STR and the program you switch to (ie. Word 2007) is irrelevant.  Step 4 and the first part of step 5 (switching to another program) must be done before tab 1 is done loading from my testing.  Switching back to FF in step 5 should be done after tab #1 is done loading.
Status: UNCONFIRMED → NEW
Component: Tabbed Browser → DOM: Events
Ever confirmed: true
Product: Firefox → Core
QA Contact: tabbed.browser → events
You need to log in before you can comment on or make changes to this bug.