Closed Bug 402367 Opened 17 years ago Closed 17 years ago

restore compatibility wrapper for getLocalizedString: for prefPanes

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
Camino1.6

People

(Reporter: alqahira, Assigned: stuart.morgan+bugzilla)

References

Details

(Keywords: fixed1.8.1.10)

Attachments

(1 file)

UserAgent uses getLocalizedString:, at least, and now somebody's throwing an exception and leaving Camino dead when trying to open it (post-de-getification).

It'd be nice if we didn't knowingly leave this broken for a1, I think, but I don't know if that's reasonable or not.
Flags: camino1.6a1?
Attached patch fixSplinter Review
Attachment #287244 - Flags: superreview?(mark)
Flags: camino1.6a1? → camino1.6a1+
Target Milestone: --- → Camino1.6
Comment on attachment 287244 [details] [diff] [review]
fix

Where's the @interface?
Withheld to protect the innocent.

Code shouldn't be compiled against those functions (especially not our own), since they are just there for binary compatibility, so they are not part of any interface, even a private one.
Comment on attachment 287244 [details] [diff] [review]
fix

worksforme sr=me
Attachment #287244 - Flags: superreview?(mark) → superreview+
Landed on trunk and MOZILLA_1_8_BRANCH. You may now return to your regularly scheduled spoofing.
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: fixed1.8.1.10
Resolution: --- → FIXED
Unfortunately, UserAgent is still hanging up on this on my 10.3.9 Mac (with the same "Camino[3363] *** -[UserAgentPref getLocalizedString:]: selector not recognized" console spew).  (It's fine on 10.5 with the very same copy of the app.)

Stuart had me try to add the @interface back, but that doesn't seem to help, either.  I don't know if I'm just horked somehow, or if there's a real issue on 10.3.9, or what :(

Comment 7 appears to have been the result of some sort of cruft in my org.mozilla.camino.plist (the recent .navigation -> .general and bundle_loader stuff relating to .privacy caused similar issues that I was smart enough to check against a fresh .plist this time around).

With a fresh .plist, I have returned to my regularly scheduled spoofing on 10.3.9.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: