4 ms·

I'm reminded of a recent security fix for IE11 that Microsoft pushed out earlier this year: https://developer.microsoft.com/en-us/microsoft-edge/platform/issue

by quink 9y ago

I'm reminded of a recent security fix for IE11 that Microsoft pushed out earlier this year: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12349663/ https://developer.microsoft.com/en-us/microsoft-edge/platfor... It killed printing from iframes completely. Great that they solved the security problem, whatever it may have been. They also broke a major piece of browser functionality that a lot of enterprises rely on fundamentally. Hell, even printing shipping labels from eBay was broken, and so was hilariously Microsoft Dynamics 365. And our own product. And the first response by Microsoft on this very link? "Won't Fix" and keep a major bit of fundamental browser functionality - printing a document - not working. "Do No Harm".

pjmlp 9y ago
Because there is a workaround, applications just need to be updated. "Either use Print Preview instead of print button or if currently using window.print() in javascript change this to document.execCommand('print’, false, null)"
- AnIdiotOnTheNet 9y ago
  > Because there is a workaround, applications just need to be updated. What actually happened: people reverted the patch. In the real world, you can't expect timely or even correct response from vendors you rely on. It sucks, but it's how it is.
  - torpcoms 9y ago
    Then after you get compromised in some way, you will start to look for better vendors.
    - AnIdiotOnTheNet 9y ago
      Only if the cost*risk of a future compromise is > cost of replacing the product. This is rarely going to be the case for business critical software.
- quink 9y ago
  > applications just need to be updated Updated away from web standards to false and null and random string. And then they made window.print work again. Additionally what guarantee was there that execCommand(magicString) where magicString is `print` wouldn’t be removed in the next security “fix” because the security fix should have broken this too as it did window.print? After all, it seems to do the same thing. Answer: none at all and then you’re back to square one.

by quink 9y ago

pjmlp 9y ago

Because there is a workaround, applications just need to be updated. "Either use Print Preview instead of print button or if currently using window.print() in javascript change this to document.execCommand('print’, false, null)"

AnIdiotOnTheNet 9y ago
> Because there is a workaround, applications just need to be updated. What actually happened: people reverted the patch. In the real world, you can't expect timely or even correct response from vendors you rely on. It sucks, but it's how it is.
- torpcoms 9y ago
  Then after you get compromised in some way, you will start to look for better vendors.
  - AnIdiotOnTheNet 9y ago
    Only if the cost*risk of a future compromise is > cost of replacing the product. This is rarely going to be the case for business critical software.
quink 9y ago
> applications just need to be updated Updated away from web standards to false and null and random string. And then they made window.print work again. Additionally what guarantee was there that execCommand(magicString) where magicString is `print` wouldn’t be removed in the next security “fix” because the security fix should have broken this too as it did window.print? After all, it seems to do the same thing. Answer: none at all and then you’re back to square one.