Closed
Bug 60868
Opened 25 years ago
Closed 25 years ago
Insert HTML button in Composer does not work with Classic and Ski Pilot themes.
Categories
(Core :: DOM: Editor, defect, P3)
Tracking
()
VERIFIED
FIXED
mozilla0.8
People
(Reporter: tarahim, Assigned: Brade)
Details
Attachments
(2 files)
|
594 bytes,
patch
|
Details | Diff | Splinter Review | |
|
2.46 KB,
patch
|
Details | Diff | Splinter Review |
New page to edit.
Insert|HTML...
Type whatever valid HTML source.
Hit Insert.
Nothing happens.
Mtrunk 2000112004
| Reporter | ||
Comment 1•25 years ago
|
||
Typo in the summary corrected.
Summary: Inset HTML broken in Composer → Insert HTML broken in Composer
I just verified that this is working in my 12/12/00 Win32 and Mac Trunk debug
builds. I was able to add images, tables, styled text, etc, all from the Insert
HTML dialog.
Marking fixed, and adding cmanske@netscape.com to Cc list.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 3•25 years ago
|
||
I do not know what a trunk debug build is, but I have seen no change in this
problem in MTrunk 2000121514, 121508, etc. If there is any other builds that
does not have this problem, fine. I expect the fix to reach nightly builds.
Until then, I keep this bug open.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 5•25 years ago
|
||
It works just fine in the NS 6 release and in my current mozilla trunk build.
You must supply exactly what you typed into the edit box for your testing.
What happens when you click on "Insert" button? Does dialog close? Do you see
anything in the document at all?
The only problem I see is that the multiline textfield appears to be "invisible"
because its background is the same color as the dialog. When you click into it,
you see a shaded border and you can type HTML source then. Initial focus should
be set automatically when dialog is opened, but that's a separate bug.
Assignee: beppe → cmanske
Status: REOPENED → NEW
| Reporter | ||
Comment 6•25 years ago
|
||
I typed the exact example in the Insert HTML window, for instance.
Whatever I type, hitting insert button does nothing.
No response whatsoever. Dialog window just remains there.
This is still true in 2000121808 MTrunk build.
Comment 7•25 years ago
|
||
Are you using a debug build? We have been seeing problems with getting the "value"
from a textfield (any textfield). That might be the problem.
Try this: Click on the toolbar "Table" icon and try to insert a table. Does it
not respond when you click on OK?
| Reporter | ||
Comment 8•25 years ago
|
||
I only test nightly binaries. Not the one with installer.
The only insert function broken is Insert HTML. Others (table, symbol, anchor
etc.) work fine.
Comment 9•25 years ago
|
||
Well thats to bad because, unfortunately, I can't reproduce the problem you
report!
| Reporter | ||
Comment 10•25 years ago
|
||
I nailed the problem. I thought it was strange that you described a background
problem that I did not see at all. That was the key. I use Classic skin and
you use Modern skin. When I changed to Modern skin, indeed Insert button worked.
Changed the summary to include this information.
Summary: Insert HTML broken in Composer → Insert HTML button in Composer does not work with Classic Skin
| Reporter | ||
Comment 11•25 years ago
|
||
BTW, a lot of Mac users prefer Classic skin because of its resemblance to
standard MacOS look. Modern skin may look cool, but does not bode well in daily
usage, IMHO.
Just fyi about other platforms:
I am running ns6, nightly builds and my own build on a win32 box. I have tested
the three basic themes, including classic. I can't reproduce your bug. The HTML
fragment I type is correctly inserted and rendered at insertion point.
Comment 13•25 years ago
|
||
The original bug here happens because of this code in dialogOverlay.js:
function doOKButton()
{
var v = document.commandDispatcher.focusedElement;
if (v && v.localName.toLowerCase() == 'textarea')
return;
We hit that 'textarea' return case. This code is obviously wrong (my guess is
that it's there to allow the return KEY to be entered in textareas in dialogs).
Why this only happens in Classic is probably focus related.
Comment 15•25 years ago
|
||
Simon: Unfortunately, that is not the problem. We are getting to our own
"doOKFunction" just fine. Some dumps reveal that in doOKButton, the focused
element is the button, not the textarea, so this isn't the cause of the
get value failure.
| Reporter | ||
Comment 16•25 years ago
|
||
Just out of curiosity, I tested Sky Pilot. It too shows this bug, and it,
neither, shows the background problem. Probably not a big deal about the fact
itself.
Changing Summary to include this information.
Summary: Insert HTML button in Composer does not work with Classic Skin → Insert HTML button in Composer does not work with Classic and Ski Pilot themes.
Comment 17•25 years ago
|
||
Hirata: Are you still seeing this problem? I tried it yesterday on a Linux
build and could not reproduce the problem.
| Reporter | ||
Comment 18•25 years ago
|
||
Yup. It is still here in 2001011104.
Has it ever been confirmed in Linux builds, BTW?
The button works fine in Modern skin just like before.
| Assignee | ||
Comment 19•25 years ago
|
||
This is a mac-specific bug (apparently). I see this on my Mac build from today.
Reassign to myself.
Assignee: cmanske → brade
Status: ASSIGNED → NEW
Hardware: Other → Macintosh
| Assignee | ||
Comment 20•25 years ago
|
||
The fix to bug #16339 seems to have broken this bug.
However, the keybindings in dialogOverlay.xul are no longer present so removing
the extra JS in dialogOverlay.js would seem to be appropriate now.
Note: Also broken (and presumably fixed with this fix) is the AddressBook New
Card dialog and Bookmarks edit dialog.
patches coming in a little bit.
| Assignee | ||
Comment 21•25 years ago
|
||
| Assignee | ||
Comment 22•25 years ago
|
||
Comment 23•25 years ago
|
||
sr=kin@netscape.com on most of the editor clean up diffs ... I'll defer
reviewing the one change about including the 2 extra overlay files to cmanske
since I'm not so sure they are neccessary.
Comment 24•25 years ago
|
||
sr=alecf on the first patch
| Assignee | ||
Comment 25•25 years ago
|
||
fixed (although there is still some related cleanup to do in editor-specific
files)
Status: NEW → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•