Closed
Bug 35590
Opened 25 years ago
Closed 25 years ago
[blocker] mail events get ignored after using mail briefly
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P1)
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: Bienvenu, Assigned: mjudge)
Details
(Keywords: smoketest)
If I read mail for more than 10 seconds or so, all events seem to get
swallowed, so that I can't read mail messages, click on buttons, use menus, etc.
Backing out your changes from around 9PM last night makes this problem go away.
If I'm confused, just mark it invalid.
Comment 1•25 years ago
|
||
marking this as a blocker just to make sure it shows up in a query. changing to
P1. I'd talked to bienvenu earlier and we could reproduce this just by
scrolling the mailnews threadpane. After that happened, we could no longer
access buttons or menus.
Severity: normal → blocker
Updated•25 years ago
|
Priority: P3 → P1
Comment 2•25 years ago
|
||
I've also backed out your changes from yesterday and have seen the problem go
away as well.
Updated•25 years ago
|
Target Milestone: --- → M16
who's changes? mine? which ones? windows only? imap? pop? are there javascript
errors?
can you give me specific steps like click on this, click on that send message
click on y ect?
Comment 5•25 years ago
|
||
Here are the steps that made it so that I could reproduce it:
Open mailnews
Open a folder that has enough messages so that a scrollbar will appear in the
thread pane.
Scroll down in the thread pane
Try to do something else and nothing will work including the trees, menus and
buttons. However, you will be able to move the window and close the window.
| Reporter | ||
Comment 6•25 years ago
|
||
as I said initially, backing out your changes from around 9PM last night fixes
this. If this is the only thing keeping the tree closed, I think backing out
your changes would be a very reasonable thing to do.
fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•