\n is not supported in logComment(), blank char in log file

VERIFIED INVALID

Status

Core Graveyard
Installer: XPInstall Engine
P3
normal
VERIFIED INVALID
18 years ago
2 years ago

People

(Reporter: David Epstein, Assigned: dveditz)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
build 2000-06-26-M17. I'll post test case after getting bug number.
1. Use \n in logComment string. in install.js file.
2. zip up archive.
3. Press Trigger. Then OK.
4. Check log file.
Result: Line break doesn't work. Char is blank.
Expected: Separate text.
Notes: 
* Line break works in alert(). 
* \t is supported in logComment. 
* \r also not supported in logComment.
(Reporter)

Comment 1

18 years ago
changed qa contact to depstein. created archive 44292.xpi in http://jimbob/bugs

log file:

-------------------------------------------------------------------------------
file:///C|/XPIStage/test/test.xpi  --  06/29/2000 19:47:42
-------------------------------------------------------------------------------

     line break test
     ---------------

     ** a bunch of text 
 next line

     Install completed successfully
     Finished Installation  06/29/2000 19:47:52
QA Contact: jimmylee → depstein
Summary: \n is not supported in logComment in log file → \n is not supported in logComment(), blank char in log file
(Assignee)

Comment 2

18 years ago
We're not going to do this one. If you want two lines with logComment() then 
call it twice :-)

alert() is a special case -- we just call the std alert() which supports this 
feature plus you can't just call it twice because two modal dialogs are not the 
same as two lines on one dialog.

logComment() is not a printf, we just dump the characters we get into the log 
as-is and whatever happens happens. It's just debugging output, I would not 
expect a finished script to contain logComments.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
(Reporter)

Comment 3

18 years ago
Oh well! :(
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.