460354 - Gmail will not allow more To: email addresses to be selected than #windows open

Status: RESOLVED WORKSFORME

(Camino Graveyard :: General, defect)

Description

[Glen A McAllister]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.17) Gecko/20080915 Camino/1.6.4 (like Firefox/2.0.0.17)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.17) Gecko/20080915 Camino/1.6.4 (like Firefox/2.0.0.17)

Have auto-complete email address on in Gmail. Select first address ok. If only one window open, no more email addresses (or partial email addresses) can be typed beyond first selection. If 2 windows open, can add another email/type something. Does not happen in Firefox 3.

Reproducible: Always

Steps to Reproduce:
1.Compose a message in Gmail
2.Try to send to more than 1 address via To: (fail)
3.Open new window. Type in another address (succeed)
4.Try to send to another address (fail).
Actual Results:  
As above

Expected Results:  
Allow as many addresses as Gmail does to be typed/selected in the To: field.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This works fine for me with only a single window open.

What happens if you try using a fresh profile?  You can use http://pimpmycamino.com/parts/troubleshoot-camino to automate this testing.

Comment 2

[Glen A McAllister]

Using a fresh profile (via Troubleshoot Camino) did not make any difference for me.

Comment 3

[Glen A McAllister]

Still a bug as of today 12/12/08 with Camino 1.6.5 (latest).

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Do you have any add-ons for Camino installed (e.g., 1Password)?  Or any
system-level input methods/"text time-savers", like TypeIt4Me, SpellCatcher,
TextExpander, etc.?

Comment 5

[Glen A McAllister]

No to anything like TypeIt4Me etc. Installed plug-ins are:
Google Talk Browser Plugin
Shockwave Flash
Default Plug-in
Java Embedding Plugin 0.9.6.4
QuickTime Plug-in 7.5.5
Flip4Mac Windows Media Plugin 2.2.1
Silverlight Plug-In
DivX Content Upload Plug-In
DivX Web Player
Google Update One-Click Installer Plugin
Google Update One-Click Deluxe Installer Plugin
RealPlayer Plugin
Verified Download Plugin

Comment 7

[Chris Lawson (gone)]

Is this:

a) still broken in 1.6.7?
b) still broken in a trunk nightly (what will become 2.0; make sure you back up your profile before testing one of these builds if you aren't already switched over to the 2.0 betas)?
c) broken in Firefox 2.x?

There have been several Gmail bugs that are Gecko 1.8-only, and I suspect this might be another example.

Comment 8

[Chris Lawson (gone)]

Glen, can you please respond to comment 7?

Comment 9

[Glen A McAllister]

(In reply to comment #7)
> Is this:
> 
> a) still broken in 1.6.7?

It isn't under Leopard, but I reported this under Tiger. I can't report if still broken under Tiger as my Tiger system will be unavailable for a couple of days (getting service)

> b) still broken in a trunk nightly (what will become 2.0; make sure you back
> up your profile before testing one of these builds if you aren't already 
> switched over to the 2.0 betas)?

Just tested in Jun 07 beta - most recent nightly beta & all ok, but again, it's under Leopard, not Tiger, so don't know if this constitutes a good test or not.

> c) broken in Firefox 2.x?

I didn't check it in FF 2.x. I'm now on 3.0.10 & ain't going back. Did you mean FF 3.x or 2.x?

I will check this again under Tiger if you want, or an older version of FF, if that's not too hard to get & install. Let me know which OS I should be testing under. 

Regards,

GAM

Comment 10

[Glen A McAllister]

I have just noticed this as being reported on the PPC platform & it wasn't - it should be Intel as I would have had my Intel Mac at the time of reporting. Apologies. Do I make the adjustment in the bug report, or someone else?

Comment 11

[Stuart Morgan]

He meant Firefox 2; Camino 1.6 and Firefox 2 are based on the same version of the underlying code (whereas the nightlies/betas of Camino 2 are based on the same code that Firefox 3 uses), so it's often helpful to know if something that works in Firefox 3 and fails in Camino 1.6 also fails in Firefox 2 and/or works in Camino 2.

If you could try one or both of Camino 2 and Firefox 2 (the later you can download from http://www.mozilla.com/en-US/firefox/all-older.html) on the machine where you can reproduce this in Camino 1.6 (once it's back from the shop) that would be great.

Comment 12

[Glen A McAllister]

Hi,

Just tried it with Camino 2 beta & FF 2.0 on a backup of my Tiger system & the bug didn't manifest on either, so it looks like it's restricted to Camino 1.6.

I'm on Leopard now & my Tiger backup is soon to be blatted with a backup of my current system, so if you want me to do anything else, please let me know a.s.a.p.

GAM

Comment 13

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Let's close this "WFM on 2.0b3" then; I don't think we'll be able to figure out what was going wrong in 1.6.x.