Edge puts a similar pressure on them, because it's the standard browser in Windows 10. There won't be a 32-bit version to fall back to for NPAPI support, so if those sites want to keep Chrome users, they _must_ offer an HTML5 access for Chrome. With Chrome the situation is much different than with Firefox. Why do you think users switch to 64-bit Firefox in the first place? Because they want to use a 64-bit browser, maybe? And if 64-bit Firefox doesn't work for them on some important sites, they might look elsewhere? The changes made have to be undone for now and another idea has to be thought of. There are hundreds of pages all over the world which people use on a regular basis.įurthermore not only Silverlight is not working Java is missing completely, too.
#Lync web app plugin download 64 Bit#
> build somewhere else? Or how do we distribute 64 bit release builds now? Do users explicitly have to download the 64 bit > Going to Mozilla's download page on, I see that we by default > for specific sites? Googling, I see that we're suppossed to be able to use
At worst case, could we whitelist Silverlight We really can't break sites like Netflix and expect that
> Microsoft's Silverlight download page says 64-bit Silverlight only Silverlight still works in 32-bit Firefox builds running on a 64-bit > Flash is the only NPAPI plugin that Mozilla supports in Firefox's Win64 > (In reply to Chris Peterson from comment #13) (In reply to Mason Chang from comment #15)
0 kommentar(er)
