Closed
Bug 57014
Opened 24 years ago
Closed 24 years ago
Use PersistentDesc strings on all platforms to Get/Set profile data
Categories
(Core Graveyard :: Profile: BackEnd, defect, P3)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: racham, Assigned: ccarlen)
References
Details
Profile code uses GetUnicodePath and InitUnicodePath so that it can handle both
i18n and ASCII data with ease. But that changed the way we store the data in the
registry. Mac which uses persistent strings and tracks down the location via
aliases has certainly seen the effect. So, we need persistent desc APIs to
get/set data in a format that will support i18n data also (bug 57011). Once that
part is fixed, this bug need to changed all those path calls to PersistentDesc
calls inthe profile manager.
I spoke to Conrad about this. There are bunch of activation regressions (of rtm
calibre). I need to looat those and that might delay the effort to fix this bug
and hence delay Conrad's efforts to proceed with embedding work. He told me that
he can take care of this and he has been working with on these issues for quite
sometime. Reassigning this bug to him and I will be following up the progress.
Assignee | ||
Comment 4•24 years ago
|
||
This no longer needs to be fixed. Another approach was taken which hides the
profile location of a registry entry in a private member of an object. The only
access to it uses nsIFile which is consistent on all platforms. The actual data
stored in the registry was kept as a unicode path on some platforms and a
persistent desc on the Mac. This allows for better backward compatibility and
isolates platform differences.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•