346464 - Cannot view typing while a sheet is open

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: HTML Form Controls, defect)

Description

[Trevor Johns]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b1) Gecko/20060728 Camino/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1b1) Gecko/20060728 Camino/1.0+

If a sheet is attached to a browser window, text entered into a form in another window will not appear until the sheet is closed.

Reproducible: Always

Steps to Reproduce:
1. Browse to a site that allows text entry.
2. Open a new window, then open several new tabs.
3. Attempt to close the new window. The window should display a sheet confirming the close.
4. While the sheet is still open, navigate back to the original window and begin entering text.

Actual Results:  
The insertion caret moves, but is not visible until the sheet is closed.

Expected Results:  
The text should be visible while typing.

Workarounds:
Right clicking within the page will cause any text already entered to become visible without having to close the sheet.

Comment 1

[Peter Jaros (:peeja)]

WFM on 2006070122 (v1.0+), 10.3.9.  I can't try a more recent build right now, but perhaps see if a fresh profile clears it.  If not, we've either got a really narrow regression window, or it's an OS version issue (if you're not on Panther).

Comment 2

[Trevor Johns]

That's odd. I just checked this on two other systems, both running Camino 1.0.2, one running 10.4.7 and the other running 10.3.9, and successfully reproduced this on both of them.

This rules out regression, and unless there's some very strange edge case where this doesn't happen on 1.0+/10.3.9 (the only configuration I didn't test) I don't think this is OS related.

Comment 3

[Peter Jaros (:peeja)]

Did you try a fresh profile?

Comment 4

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

I just repro'd this on a recent 18branch on 10.3.9.

Simon, is this at all related to bug 230346?

Comment 5

[Simon Fraser [no longer active]]

Not to bug 230346, no. Sounds a bit like the old bug 179307.

Comment 6

[Stuart Morgan]

*** Bug 354354 has been marked as a duplicate of this bug. ***

Comment 7

[froodian (Ian Leue)]

Bumping, since this clearly won't make 1.1 and is a pretty fringe scenario.

Comment 8

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

Setting this back to default milestone.

Comment 9

[Takanori MATSUURA]

This bug lies at rest in the graveyard.