Closed
Bug 20694
Opened 25 years ago
Closed 25 years ago
[dogfood][crash]Color selection in editor causes crash
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
M13
People
(Reporter: petter.sundlof, Assigned: cmanske)
References
Details
(Whiteboard: [PDT-])
This is in 1999120208, Mac OS 8.6
When I'm composing a new message and try to select a colour to assign to a
selected text element it CRASHES while trying to deactivate that selection
dialogue.
Updated•25 years ago
|
Assignee: ducarroz → beppe
Comment 1•25 years ago
|
||
reassign to editor team.
Updated•25 years ago
|
Assignee: beppe → cmanske
Comment 2•25 years ago
|
||
reassigning this to Charley for debugging
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Summary: Colour selection in 'new message' dialogue causes crash. → [dogfood]Colour selection in 'new message' dialogue causes crash.
Target Milestone: M12
Assignee | ||
Comment 3•25 years ago
|
||
It doesn't crash on Windows, but it also doesn't work (i.e., set the color)
Do any of the other color pickers crash?
For example, from any window, try Edit | Preferences | Appearance | Colors and
try to use the color picker for "text".
If that also crashes, it is a general problem and not editor-specific
Reporter | ||
Comment 4•25 years ago
|
||
It does not crash in the Preferences>Appearance>Colours dialog. It seems to be
editor-specific.
Assignee | ||
Comment 5•25 years ago
|
||
I'm not seeing any problems in Windows.
Simon and/or Kathy: Could you please investigate this for Mac? Stack trace if
it crashes?
Sujay: What happens in linux?
yes definitely a problem on Mac and Linux Charley....crashes exactly as
described .
tested in 12/4 build on Mac and 12/6 build of linux.
Updated•25 years ago
|
Target Milestone: M12 → M13
Comment 8•25 years ago
|
||
moving to M13
Updated•25 years ago
|
Component: Composition → Editor
Depends on: 20412
Product: MailNews → Browser
Summary: [dogfood]Colour selection in 'new message' dialogue causes crash. → [dogfood][crash]Color selection in editor causes crash
Comment 9•25 years ago
|
||
shorten summary and add [crash]. Add dependency to 20412 at hyatt's suggestion.
Crash is in nsMenuDismissalListener::Rollup() at the point of executing
mMenuParent->HideChain();
Charley--once Hyatt fixes 20412 you'll have an API or a way to cause the popups
to cleanup properly.
Comment 10•25 years ago
|
||
*** Bug 21735 has been marked as a duplicate of this bug. ***
Comment 11•25 years ago
|
||
should release note for M12.
Updated•25 years ago
|
OS: Mac System 8.6 → All
Hardware: Macintosh → All
Comment 12•25 years ago
|
||
Problem also happened to Linux 12-17-10-M12 commercial build.
Change platforms/OS to all.
Comment 13•25 years ago
|
||
What I see is this. I select some text, and click the color swatch on the
toolbar. The color picker comes up in some random location. I click on a color;
nothing seems to happen. I click again, and the *parent* window (i.e. the
composer window) goes away. Now, if I try to change window layering, I crash.
Assignee | ||
Comment 14•25 years ago
|
||
In the <popup> window that contains the colorpicker, the onclick handler for
the colorer picker is: "EditorSelectTextColor(); window.close()"
Calling window.close() is supposed to close the color picker (according to
hyatt), but it does noting on Windows, and it closes the parent window on Mac
and LINUX, which explains the observed behavior. This closing is obviously not
"clean" and results in crashes when other windows are clicked on.
DanM will help me look into the problem - CCing him.
Comment 15•25 years ago
|
||
window.close() is for domwindows. <menupopup>'s are not domwindow's and
therefore calling window.close() will close the domwindow. to clos ethe
menupopup, I am pretty sure you have to do removeAttribute(menupopup,"open") or
something similar to a different attribute... i don't remember what the
attribute is though. hyatt should know.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 16•25 years ago
|
||
Checked in 12/22
Comment 17•25 years ago
|
||
verified in 12/3 build.
You need to log in
before you can comment on or make changes to this bug.
Description
•