Closed
Bug 876988
Opened 12 years ago
Closed 12 years ago
Raw characters (HTML entities) displayed in MIME Type description field of Java plugins
Categories
(Core Graveyard :: Plug-ins, defect, P5)
Tracking
(firefox21 affected, firefox22- affected, firefox23- affected, firefox24- affected, firefox-esr17 unaffected)
VERIFIED
WONTFIX
People
(Reporter: hung.t.nguyen, Unassigned)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 (Beta/Release)
Build ID: 20121128204232
Steps to reproduce:
- Installed Java Plug-in 7u21
- Register Java Plug-in with Firefox 21 as making the sym link libnpjp2.so from ~/.mozilla/plugins
Actual results:
Open Firefox, about:plugins, part of the MIME Type description displayed as raw code (™)
e.g.:
IME Type Description Suffixes
application/x-java-vm Java™ Plug-in
application/x-java-applet Java™ Plug-in Applet
application/x-java-bean Java™ Plug-in JavaBeans
application/x-java-applet;version=1.1 Java™ Plug-in
application/x-java-bean;version=1.1 Java™ Plug-in
Expected results:
Comment 1•12 years ago
|
||
™ is U+0099 is "Single Graphic Character Introducer". Maybe ® is U+00AE is "Registered sign" was intended here?
Does this problem also happen for the MIME type description of any other plugins, or is it only the Java ones?
Flags: needinfo?(hung.t.nguyen)
Summary: Raw characters displayed in MIME Type description field → Raw characters (HTML entities) displayed in MIME Type description field of Java plugins
![]() |
||
Comment 2•12 years ago
|
||
Regression window(m-c)
Good:
http://hg.mozilla.org/mozilla-central/rev/8592c41069c2
Mozilla/5.0 (X11; Linux i686; rv:21.0) Gecko/20130111 Firefox/21.0 ID:20130111030906
Bad:
http://hg.mozilla.org/mozilla-central/rev/1761f4a9081c
Mozilla/5.0 (X11; Linux i686; rv:21.0) Gecko/20130112 Firefox/21.0 ID:20130112030947
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8592c41069c2&tochange=1761f4a9081c
Suspected:
42b22f0ab58c Chris Peterson — Bug 757726 - Part 1: Update about:plugins to use document.createElement() and AddonManager. r=joshmoz
![]() |
||
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
status-firefox21:
--- → affected
status-firefox22:
--- → affected
status-firefox23:
--- → affected
status-firefox24:
--- → affected
status-firefox-esr17:
--- → unaffected
tracking-firefox22:
--- → ?
tracking-firefox23:
--- → ?
tracking-firefox24:
--- → ?
Ever confirmed: true
Updated•12 years ago
|
Component: Untriaged → Plug-ins
Priority: -- → P5
Product: Firefox → Core
Updated•12 years ago
|
Comment 3•12 years ago
|
||
Can somebody please check and see whether this is the value that the plugin is giving us? We should not be parsing the plugin description as HTML, so if it is handing us HTML entities the new behavior is correct and this bug is WONTFIX.
Flags: needinfo?
Reporter | ||
Comment 4•12 years ago
|
||
It looks like it happens only for the MIME type description of Java plugin
Flags: needinfo?(hung.t.nguyen)
Flags: needinfo?
Comment 5•12 years ago
|
||
I believe that the current behavior is the "correct" one then, and the Java plugin should use UTF8 instead of HTML entities.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 7•12 years ago
|
||
Can somebody please clarify and give an example of string (with trademark sign) that the plugin should return. I tried updating the plugin code (and use UTF8) but it doesn't work either.
Comment 8•12 years ago
|
||
http://mxr.mozilla.org/mozilla-central/source/dom/plugins/test/testplugin/nptest_name.cpp#2 is an example using unicode in UTF8.
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•