Author Topic: HTML reports in Chrome not working at all ! (Read 4855 times)

mc007 · « **on:** November 29, 2012, 04:51:28 am »

well, first I could believe it but its true. check it out by self.

Eve · « **Reply #1 on:** November 29, 2012, 08:36:32 am »

I believe reports generated by the current version will display. Although the problem is that due to the security restrictions Chrome enforces you can't open it from the file system.

Of course, there is the possibility that Chrome has changed and broken it again.

skiwi · « **Reply #2 on:** December 03, 2012, 07:43:22 pm »

Quote

well, first I could believe it but its true. check it out by self.

old news

mc007 · « **Reply #3 on:** March 16, 2013, 09:31:53 pm »

hi, we just updated to ea9 and the issue still remains. that is : just unbelievable, giving the price we pay !

is this being solved in ea version 12345.0 ?

skiwi · « **Reply #4 on:** March 18, 2013, 06:40:21 am »

The comment from the chromium people is
"Run chrome with the command line --allow-file-access-from-files. Or put the html files on an HTTP server. We don't allow you to load .js and .css files when the html is a file:/// URL."
(I'd suggest that you support this request in chromium)

Eve · « **Reply #5 on:** March 18, 2013, 08:35:58 am »

If you want to further the bug report/feature request for Chrome, I note that it currently lists it as not working in Opera.

Opera provides an option which is turned off by default. (In fact if an EA report is opened when it is turned off, a link is provided to change the option.) So it really is only Chrome that has the problem, and there's nothing we can do about it other than completely re-write our report.

qwerty · « **Reply #6 on:** March 18, 2013, 09:14:16 am »

Quote

If you want to further the bug report/feature request for Chrome, I note that it currently lists it as not working in Opera.

Opera provides an option which is turned off by default. (In fact if an EA report is opened when it is turned off, a link is provided to change the option.) So it really is only Chrome that has the problem, and there's nothing we can do about it other than completely re-write our report.

I remember (but not the name) an Australian company that charged their customers for using IE for the extra effort they needed to make it work for that beast. Maybe you could do the same for Chrome

q.

Eve · « **Reply #7 on:** March 18, 2013, 11:49:38 am »

My (personal, not endorsed by Sparx Systems in any way) simple suggestion for using Chrome is to run Mongoose on the html report directory.

It works well enough for my testing purposes anyway.

Sparx Systems Forum

News: