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

Key binding may stop working after browser sits 2 hours

RESOLVED INCOMPLETE

Status

()

Core
XUL
P4
normal
RESOLVED INCOMPLETE
18 years ago
10 years ago

People

(Reporter: fenella, Assigned: saari (gone))

Tracking

Trunk
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Please see bug 27832

Per Fenella:
".. on Mac, initially, it does not work because Messenger has been up for a 
while. But when I exit and re-launch, it works fine in POP and IMAP. Also, John 
said that he has seen this problem on Linux as well"

Per John Morrision " I saw this stop working on win95 (not linux); fenella has
seen this stop working on mac after running the app for a while (in my case for 
more than 2 hours)."

I am writing this bug to keep track of this behavior.

Comment 1

18 years ago
reassigning to saari as p4 for m19.  Would be good to come up with a
reproducible case for this that didn't contain a step like running the app for a
few hours.
Assignee: trudelle → saari
Priority: P3 → P4
Target Milestone: --- → M19

Comment 2

18 years ago
mass-moving all bugs to m21 that are not dogfood+ or nsbeta2+ or nsbeta2-
Target Milestone: M19 → M21
(Assignee)

Updated

17 years ago
Target Milestone: M21 → Future
(Assignee)

Updated

17 years ago
Status: NEW → ASSIGNED

Comment 3

13 years ago
Comment #1 asks for a reproducable case. Is this bug still reproducable or is
this just from the old Mozilla Milestone-era?
If I understand the description Messenger causes a blocking error after 2 hours?
netscape is gone
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.