Closed
Bug 16931
Opened 25 years ago
Closed 25 years ago
[DOGFOOD] [Regression]Cannot type into a HTML reply message
Categories
(MailNews Core :: Composition, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: bugzilla, Assigned: sfraser_bugs)
References
Details
(Whiteboard: [PDT+])
Attachments
(1 file)
557 bytes,
text/html
|
Details |
With a build form this afternoon (cannot test with today's build because of
another identity bug, I cannot type anymore into the body when I reply to an
HTML message. The message is correctly formatted and displayed but impossible to
edit it. I will attach the html file that we load into the body (ender) that let
us reproduce the problem using just editor.
How to reproduce the problem:
----------------------------
1) open the attached reply.html file into Editor
2) try to type something in, nothing appends!
Reporter | ||
Comment 1•25 years ago
|
||
Severity: normal → blocker
Summary: [Regression]Cannot type into a HTML reply message → [DOGFOOD] [Regression]Cannot type into a HTML reply message
We will need this for tomorrow's release build - marking a blocker.
Updated•25 years ago
|
Whiteboard: [PDT+]
Assigning to charley based on the research below. Don't know if it's in our
code or mail code, but charley's the right contact on the editor team to
help fix it.
From a note I just sent to phil...
=============================================================================
Looks to me like somehow you're embedding a browser rather than an editor in the
content area. To test this, I set a breakpoint on nsEditor::nsEditor(), and
brought up the reply window. I expected to hit the constructor twice: once for
the text control in the addressing area, and once for the content. I only got
the
first one (the stack clearly shows it's a text control and not the editor app
shell.)
So I don't think Joe has anything to do with this problem. I'd have charley and
a mail UI/XUL person look at this, starting in the JS code that builds the reply
message window.
Reporter | ||
Comment 4•25 years ago
|
||
We haven't changed the way we instanciate Ender into message compose for a while (several months!). The only
difference between a new message and a reply is the .html file we load. In the first case we load a predefined file
name defaultHTMLBody.html in the second case we build on the fly a n html file. As even if I am sure at 100% that
we do the same, I will quickly do a test which consist to load the default body instead of the reply file during the
reply to see if it works...
Updated•25 years ago
|
Assignee: cmanske → sfraser
Comment 5•25 years ago
|
||
When replying, we break at nsEditorShell constructor and ::Init, but not
::InstantiateEditor.
Simon: Could you please look at this since you know more about editor startup?
(And I've had my share of firedrills this week!)
Comment 6•25 years ago
|
||
Does the file being loaded have a meta tag with "charset"? There's a known
problem with that.
Reporter | ||
Comment 7•25 years ago
|
||
I've just hardcoded the file we load into editor to be the default HTML body. Now when I reply to a message, I get the
default body and I am able do type.
The problem is somewhere else with the content of the reply file (attachment id=2317) that for some reason when
loaded into editor (you can reproduce the problem without message compose), the file is correctly displayed but you
cannot edit it.
Reporter | ||
Comment 8•25 years ago
|
||
Yes, it have a charset defined (the file is attached to this bug report):
<br><br>Jean-Francois Ducarroz wrote:<br><BLOCKQUOTE TYPE=CITE><html><META HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=UTF-8">
<html>
<head><!--doctype html public "-//w3c//dtd html 4.0 transitional//en">-->
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<br>
<table border cols="1" width="100%" bgcolor="#ffffaa">
<tbody>
<tr>
<td>
<center>
<i>This message was sent by <a href="http://www.mozilla.org/mailnews">Messenger 5.0<br></a></i></center>
</td></tr></tbody></table>
</body>
</html>
</html></BLOCKQUOTE>
Comment 9•25 years ago
|
||
Yes, this seems to have come up again. On the good side, I think I am going to
be able to remove libmime's generation of META tags for it's quoted output.
This will help MOST of the cases, but we will still have times when inline HTML
docs will be quoted into Ender and those documents could have META tags, so we
will need to fix this bug for those cases.
- rhp
Reporter | ||
Comment 10•25 years ago
|
||
In the current case, the META tag isn't created by my but inherited from the original message
Assignee | ||
Comment 11•25 years ago
|
||
I think that this is a dup of 16937. rpotts has that bug now.
Comment 12•25 years ago
|
||
I just tried this using 1999102208 build and it certainly is the META tag , but
it really isn't an issue with charset=UTF-8. The problem is really with
text/html. Shouldn't that be type=text/html? If I rewrite the META element
contnent to this:
<META HTTP-EQUIV="Content-Type" CONTENT="type=text/html; charset=UTF-8">
it works just fine.
Comment 13•25 years ago
|
||
I didn't think that syntax was correct. If I look at the syntax used in the
Netscape Japan page, the line is:
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=x-sjis">
- rhp
Comment 14•25 years ago
|
||
well, the HTML 4.0 spec, in section
http://www.w3.org/TR/REC-html40/struct/global.html#edef-META
shows the character encoding example this way:
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-5">
which is how it is written out in the file, so apparently we shouldn't put in
the type=
the really weird thing, is that I swapped the content to this:
content="charset=ISO-8859-5; text/html"
and it works
Comment 15•25 years ago
|
||
*** Bug 17073 has been marked as a duplicate of this bug. ***
Updated•25 years ago
|
Whiteboard: [PDT+] → [PDT ]
Comment 16•25 years ago
|
||
PDT+ was accidentally changed to just PDT. I'm changing it back.
Comment 17•25 years ago
|
||
changing QA assigned to myself
Comment 18•25 years ago
|
||
Rick's changes on Sunday fixed this problem I believe. It seems to be working
for me now.
Reporter | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 19•25 years ago
|
||
Problem gone. Mark it fixed. Thanks rickg.
Comment 20•25 years ago
|
||
Actually it was the other Rick...Rick Potts =)
Comment 21•25 years ago
|
||
Win32 (1999-10-26-09 M11)
I can type into a HTML reply message now.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•