Closed Bug 34056 Opened 24 years ago Closed 24 years ago

Cannot type in composer without resizing window first.

Categories

(Core :: DOM: Editor, defect, P1)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: shrir, Assigned: eric)

References

Details

(Keywords: regression, Whiteboard: [PDT+])

Using today's linux commercial build 2000033109

1. Install and launch the browser
2. Launch composer using Tasks-> Composer
3. Try to click mouse on the page but no cursor appears. If I close Sidebar, I 
   can type text.
4. Also, if composer launches without sidebar, then I cannot type anything 
   unless I launch the Sidebar....spooky !!
happens on windows also....
I see this on windows commercial bits too. Mac build not yet out... marking OS: 
all.
OS: Linux → All
assigning to sfraser
Assignee: beppe → sfraser
Priority: P3 → P1
Target Milestone: --- → M15
this affects mail compose also.  per simon, will track that issue here as well 
I don't think it has anything to do with sidebar. If you simply resize the
window, that allows you to click in the content area and type. Closing or
opening sidebar is probably just causing the same relayout that resizing does.
This is a weird one!
I'm looking at this now. Initial reaction is that it is not a regression caused 
by my frameset-detection code, but is some kind of event handling problem.
Status: NEW → ASSIGNED
Agreed that this has nothing to do with the sidebar.  I keep the sidebar closed,
yet I'm seeing this bug today on linux. 
Summary: Cannot type in composer if sidebar is open → Cannot type in composer without resizing window first.
This ain't my bag, baby. It's some event/focus problem; the editor is properly 
created, and is ready to handle events, but it never gets the keypresses until 
you resize.
Assignee: sfraser → saari
Status: ASSIGNED → NEW
Note that if you open an existing file, it doesn't display in the content
window until you resize the application window.
I didn't do it! Guess I'll start slogging through tinderbox.
Status: NEW → ASSIGNED
Keywords: beta2, regression
This seems like a fairly serious regression -- it gives people the impression
that they can't use the editor at all.  Any progress on figuring out what might
have regressed?
I think 34084 is a dup of this bug, marking as such
*** Bug 34084 has been marked as a duplicate of this bug. ***
Oh Eric, I think this is yours.
Assignee: saari → evaughan
Status: ASSIGNED → NEW
Hardware: PC → All
Also affects IM compose window.
I'd like to mark this dogfood instead of beta2 due to frequency of someone 
running into this and not realizing the workaround.
Keywords: beta2dogfood
pdt+
Whiteboard: [PDT+]
*** Bug 34121 has been marked as a duplicate of this bug. ***
fixed
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
*** Bug 34682 has been marked as a duplicate of this bug. ***
*** Bug 34682 has been marked as a duplicate of this bug. ***
verified in 4/6 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.