NPAPI difference between Firefox and chrome
Hi, I'm writing some plugin; I got Gesko SDK from mozilla site; After build it successfully loaded and working on Firefox; I tried to load and execute it with chrome; I found that chrome cannot load plugin; After some debugging I found that plroblem in function table structures - size of structures is not the same in firefox and chrome; Additional search bring me to a difference - it is in alignment; Firefox and Gesko using 32 bit alignment/packaging, and chrome use 8 bit alignment/packaging; So, my questions are: -is it bug of chrome or firefox? -when will it be fixed? -I did not work with chrome previously; from when is this build difference?
Ausgewählte Lösung
This forum is geared toward Firefox end user support, not toward developers, so you may not get an answer from anyone who knows exactly what you are talking about. Not to sound rude, but if your plugin is working in Firefox, but not in Chrome wouldn't it make sense to ask a Google support forum about your Firefox plugin not working in Chrome?
As far as 8-bit vs. 32-bit, AFAIK 8-bit operating systems and programs date back like 20 years, so I doubt if Google is using 8-bit in its' plugins. But that would best be addressed by someone familiar with Chrome development and plugins.
Diese Antwort im Kontext lesen 👍 0Alle Antworten (2)
Ausgewählte Lösung
This forum is geared toward Firefox end user support, not toward developers, so you may not get an answer from anyone who knows exactly what you are talking about. Not to sound rude, but if your plugin is working in Firefox, but not in Chrome wouldn't it make sense to ask a Google support forum about your Firefox plugin not working in Chrome?
As far as 8-bit vs. 32-bit, AFAIK 8-bit operating systems and programs date back like 20 years, so I doubt if Google is using 8-bit in its' plugins. But that would best be addressed by someone familiar with Chrome development and plugins.
I asked in both forums:)