358927 - plugins now work in UTF-8, but there is no way to detect that

Status: RESOLVED INVALID

(Core Graveyard :: Plug-ins, defect)

Description

[William Bardwell]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

With FireFox 2.0 (and Mozilla ?.? presumably), the plugins apparently now get everything as UTF-8 on Windows.  But the version returned from NPN_Version() was not changed at the same time that this HUGE change in the plugin API was made, so there is no way for a plugin to tell what encoding stuff is going to be in.  It is not even clear what version numbers to look for in the UserAgent string to detect that a plugin is running under the new world order.

Reproducible: Always

Steps to Reproduce:
1.  Make a plugin, try to handle URLs or setting status or anything
2.  Suprise, it is now UTF-8 instead of the host code page
3.  **** your pants.

Actual Results:  
Everything is UTF-8, but looking for version 16 covers late FireFox 1.5 and FireFox 2.0.

Expected Results:  
The plugin API version number should have been incremented when this change was instituted, now, I guess maybe add a new thing to NPN_GetValue for what the current code page is?  Or at least publish what version numbers to look for in the UserAgent to detect that this is the case.

Comment 1

[aravindm]

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.4) Gecko/20100413 Firefox/3.6.4
Please update if you are able to still reproduce with the latest nightly build  ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/

Comment 2

[William Bardwell]

That reproduction request makes no sense, the bug is that there is no API to
tell what encoding the browser is going to use for URLs and such.

Comment 3

[Ed Morley [:emorley]]

Comment 1 was a mass message of old bugs, presume aravindm misread this bug.

Either way, this issue presumably can be closed since it was about the plugin API version not being incremented for Firefox 2.0. However, since the oldest supported Firefox version is 3.5/3.6, plugins can assume Firefox will be providing them with UTF-8 strings, so no need for plugins to have an API to find this out surely?

Comment 4

[Ed Morley [:emorley]]

Whiteboard closeme date been and gone, so marking as invalid per comment 3.

Please comment on/reopen this issue if you feel this is incorrect.