AngularJS ng-hide print issue

Issue #7289494 • Assigned to Bogdan B.


Radu S.
Apr 21, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 9 people

Sign in to watch or report this issue.

Steps to reproduce

By default AngularJS injects a style tag with properties for the ng-hide CSS class used in the ng-show & ng-hide directives.

    display:none !important;

During normal browsing everything works as expected, but when printing, elements that should be hidden (have ng-hide class) are visible both in the print preview and in the final output.
If we add only the ng-hide class properties again in our own style tag everything works fine.

    display: none !important;

Example in attachment!

Microsoft Edge 25.10586.0.0
Microsoft EdgeHTML 13.10586
AngularJS 1.4.9
It works as expected in Internet Explorer 10 & 11


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Bogdan B.”

  • Same buggy behavior with the Windows 10 Anniversary Update.
    Microsoft Edge 38.14393.0.0
    Microsoft EdgeHTML 14.14393

  • Additional info: We’re using Kendo UI Mobile with AngularJS. Only the first print action honors ng-show/ng-hide. Any subsequent print action (i.e. just pressing the “print” button a second time without touching Edge otherwise in between) does not honor ng-show/ng-hide. It doesn’t matter which print output one chooses. The hidden elements show up already in Edge’s print preview.

  • The only working strategy for us is to close/restart Edge, then we are able to print 1 single time, then to close/restart Edge…

  • I just tried the example provided by the original OP. We experience the same effect. If you open the print dialog the first time, then everything’s fine. If you open the print dialog any subsequent time, then the hidden elements are incorrectly visible - already in the print preview.

  • I also now noticed that one does not need to close/restart Edge. A page refresh does suffice to be able to print correctly again 1 single time.

You need to sign in to your Microsoft account to add a comment.

Sign in