: K-Meleon Forum
K-Meleon development related discussions.
[quote=guenter] [quote=deadlock] One of the last changes for KM1.6b3 could be a working plugin-check. It works in KM1.54. [url=https://www.mozilla.com/en-US/plugincheck/]www.mozilla.com/en-US/plugincheck/[/url] Failure caused by GRE or Chrome changes from 1.8.1 to 1.9.1.. I have no idea, why nobody tried to fix that in the past two years. There are enough open bugs left for KM1.6 release candidate and most of latest changes in KM1.6b3 should be useful for KM1.7.[/quote] 1.) The plugins page error is in https://www.mozilla.com/en-US/plugincheck/ in this line 672/673. checkPlugins('https://plugins.mozilla.org/pfs/v2'); The document which it refers too: contains "" I assume that it calls default code from GRE191 source tree that is located in: ./toolkit/mozapps/plugins... Which AFAIK lands in toolkit.jar during build. K-Meleon does currently not use/have this part of toolkit. This source tree part contains no xpt or dll as far as I can see. Possibly: ./components/plugins.xpt & pluginGlue.js could help to do the job. They are part of K-Meleon 1.6 GRE. No idea whether they work? 2.) I agree. If bugs are fixed for a 1.6 version it can be probably reused. I am not competent to say whether the open bugs are show stoppers that must be fixed before coders/devs can move on to the next version. So I can only agree with deadlock's evaluation.[/quote]
K-Meleon forum is powered by