Great News. While some like myself are holding out for Windows 12 with better expectations than 11 has thrown a cueve with. I always felt Adobe Acrobat reader was cutting edge and the perfect fit for Windows O/S straight up from the beginning and with time tested stamina.
well, microsoft re-invented the plugins again. ofc it had reason to ban this crap from the browsers, why should microsoft care? and i see admins crying rivers. it need a lot more rules now, and its already visible that the acrobat engine is advertising an adobe account. another point to mention that the acrobat engine has 45megs without other components, it will blow edge for more than 60 megs, maybe hundred. winwin for both - ms do not has to take care of the really good opensource pdfjs, and adobe will gain some more money in selling pro features as an account. lose for customers and the rest - raised options to intrude and more work to administrate an already abandoned software.
I must say that it first I thought you was being sarcastic. Let's not forget about what a security disaster Adobe Acrobat's plugin was for browsers. So I wonder if this will re-introduce security holes into Edge. I mean what's next, perhaps baking in Macromedia Flash?
It seems that I will associate the PDF files back to LibreOffice or Firefox then instead. But will set pdfjs.enableScripting to false. I used Edge's Viewer, since the PDF viewer built into Edge doesn't execute the JavaScript embedded in the PDF. For work Adobe, Foxit, Sumatra etc. are indeed more useful, but only for reading purposes, browsers built in PDF viewer is more than enough for me.
