Closed Bug 138195 Opened 22 years ago Closed 22 years ago

Create New Tab, text focus does not follow

Categories

(SeaMonkey :: Tabbed Browser, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 124750

People

(Reporter: tcharlesyun, Assigned: jag+mozilla)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
BuildID:    2002031104

To start, I type very quickly and potentially overuse shortcut keys...

So, the non-fatal bug that I have noticed:
- Use CTRL-T to open a new tabbed browser
- The cursor focus automatically jumps to the URL entry area
- Type in a URL, call it Tab1, and press enter
* IMMEDIATELY after you press enter, press CTRL-T to open a new tab, call it Tab2
- one would expect cursor focus to be in the URL area for Tab2, but...

- If Tab1 has javascript or something that autofocuses the cursor into a web
form, then your typing will occur in the background tab, not in the URL area for
Tab2.  (Google does this on their site) 

I did not think this was a big problem until I started typing in some
information for web hosted mail acct.  I loaded Google in the background, opened
a new tab, (note: i was not paying close attention) entered in the URL for the
web mail acct, and then entered in the user/pass... and noticed that my typing
was not showing up.  I did not notice that the text was being entered into the
background window until I closed the top (in Z order) tab.




Reproducible: Always
Steps to Reproduce:
- Use CTRL-T to open a new tabbed browser
- The cursor focus automatically jumps to the URL entry area
- Type in a URL, for Tab1, and press enter
* IMMEDIATELY after you press enter, press CTRL-T to open a new tab, call it Tab2
- one would expect cursor focus to be in the URL area for Tab2, but...

- If Tab1 has javascript or something that autofocuses the cursor into a web
form, then your typing will occur in the background tab, not in the URL area for
Tab2.  (Google does this on their site) 


Actual Results:  Typed text was entered into the wrong tabbed browser (or, text
was entered into a tab that was not visible)

Expected Results:  All text entered by a user should show up in only the viewed
tab.  If cursor focus is grabbed by a page, it should be limited to that page.

If one waits a bit longer after entering a URL for Tab1, Moz will "lock up" and
not allow a new tab to be created until Tab1 is rendered.  This seems to solve
the problem.  

My assumption is that by entering the URL and creating a new tab immediately
after, I am somehow bypassing whatever safe-check system that is already in place.

*** This bug has been marked as a duplicate of 124750 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
marking verified as a duplicate.

if you decide to reopen this bug, please clarify why.

search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.