If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

"xmlencoding detect- ISO-8859-1" per page load in release builds

VERIFIED FIXED in mozilla0.9.4

Status

()

Core
HTML: Parser
P2
normal
VERIFIED FIXED
16 years ago
16 years ago

People

(Reporter: John Morrison, Assigned: harishd)

Tracking

({topembed})

Trunk
mozilla0.9.4
topembed
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fixed on the trunk and branch], URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
The message "xmlencoding detect- ISO-8859-1" (or whatever charset) is being 
printed with each page load in release builds. This needs to be turned off,
and really should be turned off in the 0.9.2/RTM branch (i.e., I don't 
really care about this being in trunk builds, but end users don't need to 
see this kind of stuff).
(Reporter)

Comment 1

16 years ago
Created attachment 42628 [details] [diff] [review]
Patch (or whatever variation that cuts out the naked printf).
(Reporter)

Comment 2

16 years ago
Just to note (not that harishd and vidur don't know this), but this landed 
as part of the fix for PDT+ bug 81253.
Keywords: mozilla0.9.3
(Assignee)

Comment 3

16 years ago
Yikes. We should fix this.
Status: NEW → ASSIGNED
Whiteboard: nsBranch
(Assignee)

Updated

16 years ago
Target Milestone: --- → mozilla0.9.3

Comment 4

16 years ago
r=nisheeth
sr=jst

Updated

16 years ago
Keywords: nsBranch
Whiteboard: nsBranch
(Assignee)

Comment 6

16 years ago
Fixed on the trunk.
(Assignee)

Updated

16 years ago
Whiteboard: [fixed on the trunk]

Comment 7

16 years ago
We couldn't get a PDT approval on this.  Removing nsBranch and marking fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Keywords: nsBranch
Resolution: --- → FIXED
(Reporter)

Comment 8

16 years ago
Just noting that per bug 76720, this was a priority for an embedded customer:
To quote the manager-formerly-known-as-phil: "My must-have is no console output 
(or memory use from redirected output) on Linux optimized builds."

Personally, I don't care, but it seems that adding '//' before the printf
to satisfy this embedding customer is pretty high in reward-to-risk terms.
(Reporter)

Comment 9

16 years ago
I am told that marek may wish to take this on the branch post 6.1. Marek?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 10

16 years ago
Moving to more realistic target - m0.9.4!
Target Milestone: mozilla0.9.3 → mozilla0.9.4
(Assignee)

Updated

16 years ago
Status: REOPENED → ASSIGNED
Priority: -- → P2
(Assignee)

Updated

16 years ago
Keywords: topembed
(Assignee)

Comment 11

16 years ago
Fixed on the branch
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago16 years ago
Resolution: --- → FIXED
Whiteboard: [fixed on the trunk] → [fixed on the trunk and branch]

Updated

16 years ago
QA Contact: bsharma → moied

Comment 12

16 years ago
Verified fixed checked in cvs (rev 3.257)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.