Closed Bug 31752 Opened 20 years ago Closed 18 years ago

[tracking]U+0100 ~ U+FFFF data damage when JavaScript pass to string in idl

Categories

(Core Graveyard :: Tracking, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

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.
Status: NEW → ASSIGNED
Keywords: meta
Target Milestone: M17
Depends on: 31246
Depends on: 31288
Blocks: 31758
Target Milestone: M17 → M20
meta bug. mark it as future to make it out of the radar
Target Milestone: M20 → Future
Component: XPConnect → Tracking
Target Milestone: Future → mozilla1.0
Keywords: mozilla1.0
tracking bug go 1.1
Target Milestone: mozilla1.0 → mozilla1.1
move all my "tracking" bug to "M1"
Target Milestone: mozilla1.1 → M1
clearing milestone
Target Milestone: M1 → ---
move tracking bug to M1
Target Milestone: --- → M1
this tracking bug lost it's meaning now. mark it as won'tfix
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.