User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6a) Gecko/20031001 Firebird/0.7+ (aebrahim) Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6a) Gecko/20031001 Firebird/0.7+ (aebrahim) This is intended to be a compilation of Bugs/Issues for users you are attempting to use advanced features (Javascript/CSS/Inline Styles) in Mail-News My primary interest here is the use of these capabilities in Newsgroups. Attempts will be made to identify these issues as "Thunderbird specific" or pertaining to the Moz trunk. Reproducible: Always Steps to Reproduce: 1. 2. 3.

http://bugzilla.mozilla.org/show_bug.cgi?id=229122 (Ampersand) and (greater than) characters are escaped in Javascript included in the body. This requires completely avoiding those operators to maintain function. Evidently the concensus of opinion is that Javascript operators should not be protected from escaping by the script tags. Script in body is a common practice in stationary groups.

http://bugzilla.mozilla.org/show_bug.cgi?id=224733 After using |edit|select all then insert HTML, any editing results in busting the links of all previously inserted images. Images must be re-inserted or the escaped url corrected within the edit.

http://bugzilla.mozilla.org/show_bug.cgi?id=225441 Attempting to reply in HTML mode to a message with Embed tag results in a blank page in composer, and a blank page for the recipient.

http://bugzilla.mozilla.org/show_bug.cgi?id=234056 Cursor disappears when editing text over positioned elements. See my attachment there for an easily reproduceable example.

http://bugzilla.mozilla.org/show_bug.cgi?id=232714 An example of rendering performance problems. Additional comments: Cpu utilization in script execution, seems to be much higher than the suite in Thunderbird. ? the lack of a disc cache.

http://bugzilla.mozilla.org/show_bug.cgi?id=192557 Meta and title tags inserted in body. Addresses some serious issues in templates, and editing head element.

Joe, it'd be really helpful if you marked this bugs as blockers of this bug instead of just putting the bug in the comment field. That let's all of us look at this bug as a tracking bug...Thanks for putting together this list.

Joe, is this list still useful? Note: pretty sure 232714 no longer occurs

(In reply to comment #8) > Joe, is this list still useful? Note: pretty sure 232714 no longer occurs I'll update the list, and bug 232714 is probably semi-fixed Although bug 372039 is probably related.(at any rate this would be a core issue) As to the usefulness, bugs are only useful if there are interested parties with the time and skills necessary to fix them. </rant>

Example: Bug 192557 still lives and proliferates like rabbits. Some cases more Meta tags are added with each use of Insert HTML edit. Joe, if You need help with editbugs get with me offline.

(In reply to Ronald Killmer from comment #10) > Example: Bug 192557 still lives and proliferates like rabbits. Ronald, That bug report was closed long ago. Do you have a new bug number?

(In reply to Wayne Mery (:wsmwk) from comment #11) > (In reply to Ronald Killmer from comment #10) > > Example: Bug 192557 still lives and proliferates like rabbits. > > Ronald, That bug report was closed long ago. Do you have a new bug number? That was a long time ago on the way toward TB2. Need to get the attention of Joe, the OP of the blocker list. http://bugzilla.mozilla.org/show_bug.cgi?id=229122 is no longer a valid issue since we killed JS access of embedded external scripts around the TB3 or TB3.1 release prep time (CAPS core change caused). I think this tracker can be closed as the one remaining blocker, https://bugzilla.mozilla.org/show_bug.cgi?id=229122 should be resolved wontfix for reason stated above.