![not seeing screenshare lync web app not seeing screenshare lync web app](https://slideplayer.com/11/3014203/big_thumb.jpg)
- #Not seeing screenshare lync web app movie
- #Not seeing screenshare lync web app 64 Bit
- #Not seeing screenshare lync web app update
- #Not seeing screenshare lync web app download
- #Not seeing screenshare lync web app windows
#Not seeing screenshare lync web app movie
Using pre-release software is a little bit like being in a movie test audience in that you're not looking at the final product and the ending may change. The effect of this is that we see a change in pre-release channels.
#Not seeing screenshare lync web app update
> force developers to update the back end.Ħ4-bit Firefox has never been released so Silverlight support hasn't been withdrawn, rather it looks like it will never be offered in the first place. > Breaking the experience for the client/user is a terrible way to try and > some fires lit but until that change happens, your users will jump ship toģ2-bit Firefox works and people already have it installed. Mozilla choosing to stop supporting the plugins will get > seem to really care as much about the overall user's experience versus their > making the decisions and providing guidance on where Mozilla is going don't It seemed abundantly clear the the people > It wasn't intended to be harsh, merely stating that it's amazing how out
![not seeing screenshare lync web app not seeing screenshare lync web app](https://support.content.office.net/en-us/media/d63c7b57-b367-4cb3-b98a-2214b17d3a8d.png)
I was lucky enough to find a forum post where someone had mentioned that you could still force Firefox, for at least that current version, to override the forced signature if you dived into the config but that didn't bring back Silverlight.īreaking the experience for the client/user is a terrible way to try and force developers to update the back end. It was great to be chugging along with my work only to have Firefox crash and then when it reopened, none of the plugins I needed to get back to where I was two minutes prior were allowed to run anymore. There was no "warning these won't work in the future" it just completely disabled them and refused to even acknowledge Silverlight existed. It was said that there would be warning in V41. I can totally understand making things idiot proof, I have to deal with that at work daily but to completely remove any way to override it after the fact, knowing fully well that most people are set to automatically update is just inane. Mozilla choosing to stop supporting the plugins will get some fires lit but until that change happens, your users will jump ship to whatever browser works. It seemed abundantly clear the the people making the decisions and providing guidance on where Mozilla is going don't seem to really care as much about the overall user's experience versus their own priorities. It wasn't intended to be harsh, merely stating that it's amazing how out there the replies I reading were. In the end we have a chicken-and-egg problem here: fewer people than possible will adopt Firefox 64-bit because it doesn't work on sites important to them, and those sites won't adapt to Firefox 64-bit because too few people use it. Note that some of those sites already do offer an HTML5 access for Chrome, but not for Firefox, so I wouldn't expect Firefox 64-bit to suddenly and miraculously work when Chrome 45 and Edge gain user share. With Firefox 64-bit most of them won't invest any time and money, because there's still the 32-bit version that works.
#Not seeing screenshare lync web app windows
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.
#Not seeing screenshare lync web app 64 Bit
> build somewhere else? Or how do we distribute 64 bit release builds now?
#Not seeing screenshare lync web app download
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
![not seeing screenshare lync web app not seeing screenshare lync web app](https://www.add-in-express.com/creating-addins-blog/wp-upload/images/2011/lync-online/lync-interface.png)
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)