Closed Bug 620140 Opened 14 years ago Closed 14 years ago

Bug 616271 causes CanLoadPlugin returns failure when plugin path is non-ASCII

Categories

(Core Graveyard :: Plug-ins, defect)

All
Windows 7
defect
Not set
normal

Tracking

(blocking2.0 betaN+)

RESOLVED FIXED
mozilla2.0b9
Tracking Status
blocking2.0 --- betaN+

People

(Reporter: m_kato, Assigned: m_kato)

References

Details

(Keywords: regression)

Attachments

(1 file)

nsIFile::GetNativePath() doesn't return UTF-8 charset on Windows.  (ex. JPN version is CP932.)  So, if plugin path is no-ASCII, CanLoadPlugin always return PR_FALSE.
Attached patch fix v1Splinter Review
Attachment #498674 - Flags: review?(joshmoz)
Attachment #498674 - Flags: review?(joshmoz) → review+
Attachment #498674 - Flags: approval2.0?
blocking2.0: --- → beta9+
http://hg.mozilla.org/mozilla-central/rev/6d22eaba6e95
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b9
Attachment #498674 - Flags: approval2.0?
As per today's meeting, beta 9 will be a time-based release. Marking these all betaN+. Please move it back to beta9+ if  you believe it MUST be in the next beta (ie: trunk is in an unshippable state without this)
blocking2.0: beta9+ → betaN+
No longer blocks: 616271
Blocks: 616271
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: