Closed
Bug 31752
Opened 25 years ago
Closed 23 years ago
[tracking]U+0100 ~ U+FFFF data damage when JavaScript pass to string in idl
Categories
(Core Graveyard :: Tracking, defect, P3)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
WONTFIX
M1
People
(Reporter: ftang, Assigned: ftang)
References
Details
(Keywords: meta)
Currently, several idl files define the data type as string while it should
really define then as wstring. This cause some data lostage by xpconnect while
convert JavaScript object which hold unicode string and convert to const char*
in C++ . The worst part is we currently have no system to track these problem.
We should add some assertion code so incase we hit some value which is >= U+0100
we will through exception or assert. This bug is the tracking bug for all of
these problem. This bug is similar to 28424 but not the same since it seems does
not depend on nsString . I will create a seperate bug for implementation the
error checking and we should mark all the bug we found block this bug.
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Target Milestone: M17 → M20
Assignee | ||
Comment 1•25 years ago
|
||
meta bug. mark it as future to make it out of the radar
Target Milestone: M20 → Future
Assignee | ||
Updated•23 years ago
|
Component: XPConnect → Tracking
Target Milestone: Future → mozilla1.0
Updated•23 years ago
|
Keywords: mozilla1.0
Assignee | ||
Comment 3•23 years ago
|
||
move all my "tracking" bug to "M1"
Target Milestone: mozilla1.1 → M1
Assignee | ||
Comment 6•23 years ago
|
||
this tracking bug lost it's meaning now. mark it as won'tfix
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•