Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report paging does not work in Microsoft Edge or IE? #49

Open
c3rberus opened this issue Sep 30, 2019 · 25 comments

Comments

@c3rberus
Copy link

commented Sep 30, 2019

When I create a HTML report using New-HTML and view it in Chrome everything looks good, the data tables show 15 records and have a pager for more data.

If the same report is open under MS Edge or IE it shows all the records on one page (there is no pager). This makes it very difficult to use because you end up with a huge page scroll without paging. This was tested on latest Windows 10 1903.

Is it possible to get the paging to work for Edge/IE or am I missing some parameter?

@c3rberus c3rberus changed the title Issue with Microsoft Edge? Report paging does not work in Microsoft Edge or IE? Sep 30, 2019
@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Sep 30, 2019

All the hard work is done by JavaScript. Not sure if IE will be able to handle advanced JS but that’s what you need to get it running. I use Edge Chromium myself. For standard Edge it could possibly work I guess but you need to make sure JavaScript for local files is allowed. Of course it’s possible that both products are so legacy some features of modern internet Won’t work.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Sep 30, 2019

In other words, what you did in Powershell is enough. The hard part is now verification whether IE or non-chromium Edge can be used with it.

@c3rberus

This comment has been minimized.

Copy link
Author

commented Sep 30, 2019

I am using Edge with the default settings from a Windows 10 install (not domain joined so no group policy settings are being applied to harden it). This should be fairly easy to reproduce if you load a larger data table in Edge. I don't think there is any blocking going on. The report worked fine in ReportHTML but once I converted over to PSWriteHTML the bug is there in Edge.

When I open in Edge and use F12 to review, there is no error loading any of the required components. Everything else seems to work fine (tabs, icons, search filter, export buttons).

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Sep 30, 2019

I could always reproduce it. I just assumed this won't work on IE or Edge. But actually I can see that indeed it works if I open up: https://datatables.net/examples/advanced_init/complex_header.html

So maybe it's just my implementation that is struggling. I don't promise a fix this week as I'm on delegation to France, but if I'll get a chance I'll try to push some checks and see what may be causing this.

@c3rberus

This comment has been minimized.

Copy link
Author

commented Sep 30, 2019

Sounds good, thanks for the quick replies.

@PrzemyslawKlys

This comment has been minimized.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Sep 30, 2019

Actually, it seems to be working fine: https://evotec.xyz/wp-content/uploads/2019/05/DashboardActiveDirectory.html when hosted on the website. This mean it only doesn't work for local files. This seems more like an issue with IE/Edge with the way I'm including those scripts.

@c3rberus

This comment has been minimized.

Copy link
Author

commented Oct 1, 2019

You are right, only seems to be when the file is open locally vs. hosted. That is super strange, I wonder what causes it to break locally.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 2, 2019

Does it work locally with ReportHTML?

@1RedOne

This comment has been minimized.

Copy link

commented Oct 7, 2019

Could you give some simple reproduction steps? I can help diagnose what could be happening to the JS.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 7, 2019

Just take an example - for example, Example04-TableAndTabs and see how the Table loads in Chrome/Firefox and how it acts in IE. Basically JS doesn't seem to load properly. Or

Get-Process | Out-HTMLView

And try the .html in diff browsers.

@1RedOne

This comment has been minimized.

Copy link

commented Oct 8, 2019

I tried downloading all of the JS, and basically everything related to this issue and can't find a workaround. Seems that both IE and Edge just happen to suck.

Works fine in FireFox, Chrome, EdgeDev, and everything else one might use.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 8, 2019

@c3rberus Do you know if ReportHTML reports happen to work on IE/Edge when run locally?

@1RedOne Ye, it's a bit of pity. IE is only available on servers for me.

@c3rberus

This comment has been minimized.

Copy link
Author

commented Oct 9, 2019

Does not work in IE/Edge when ran locally. We use Edge as default browser within the organization and everyone has Chrome installed as a secondary option. Edge plays nice with internal enterprise applications so we can't switch out the Windows 10 default quite yet. It would be great if we could make this work for IE/Edge. I wonder what is causing this, the datatables show being compatible and no errors are thrown when the html file is opened.

@1RedOne

This comment has been minimized.

Copy link

commented Oct 9, 2019

This is caused by Internet Explorer and Edge's behavior of not loading JavaScript files for items in the Intranet zone. I cannot find a workaround other than changing the setting in Internet Explorer.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 9, 2019

Did you manage to find settings that work?

I was thinking I need to try this out https://stackoverflow.com/questions/8146926/why-does-ie-restrict-the-javascript-files-of-local-html-pages with crlf.

PrzemyslawKlys added a commit that referenced this issue Oct 9, 2019
@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 9, 2019

@1RedOne

This comment has been minimized.

Copy link

commented Oct 9, 2019

@c3rberus

This comment has been minimized.

Copy link
Author

commented Oct 16, 2019

Did it work for you when you try changing zone info? What did you change exactly? IIS will likely be the route we take but curious about the zone info change you speak of.

@1RedOne

This comment has been minimized.

Copy link

commented Oct 17, 2019

No, even when I changed zone info using every possible trick, I could not get this to work.

PrzemyslawKlys added a commit that referenced this issue Oct 18, 2019
@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 18, 2019

I've tracked this to Datatables 1.10.12 working fine, where 1.10.13+ doesn't work. But it only doesn't work if used with my code.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 18, 2019

This folder has 2 files: https://github.com/EvotecIT/PSWriteHTML/tree/master/Examples/Example-IE

Both should work in IE. One is mine with 1.10.12, one is using some random example where I've put a similar version.

This needs further debugging why it fails for higher versions.

@PrzemyslawKlys

This comment has been minimized.

Copy link
Member

commented Oct 21, 2019

This was fixed by DataTables on the error I've reported on their forum. Fix is here: DataTables/DataTablesSrc@91c48a1

Currently its part of nightly version, until then I guess we will use 1.10.12 so I will downgrade DataTables for next release but this will give us full IE support back.

I'm still waiting for VIS support for IE: visjs/vis-network#166 which would allow diagrams to work in IE as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.