I am trying to implement SSRS Report Viewer 2016 control on my Webpage
I did install package Microsoft.ReportingServices.ReportViewerControl.WebForms -Pre it is now on version 140.1.291.2731477-rc
When I open page whit report-viewer it looks all right .
When I try to print on chrome
I get Print dialog for Page orientation and page size.
After click on print, nothing happend.
On chrome developer tools in console screen get message:
Resource interpreted as Document :
Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=14.0.1.291&Name=Microsoft.Reporting.Web…
but transferred with MIME type application/pdf: http://localhost:54071/Reserved.ReportViewerWebControl.axd?ReportSession
If I try to print in EDGE i get print screen dialog without problems.¸(PDF get oppened)
If I try on Firefox I get PDF opened inside Dialog Window.
Does printing in chrome requierd ADOBE extension.
I do open PDF-s inside chrome whitout problems.
Can this issue be caused becouse report viewer control rendering report hosted on SSRS2012 services. (Control is 2016 ver but it render remotely hosted SSRS2012 reports).
Related
I have a simple app deployed in GitHub pages (my web-app). The app has some inputs and I tried to use it offline on my Android phone, by clicking the download button on Chrome, which downloads the HTML; but all the inputs and buttons are disabled.
If I click the file that was downloaded in 'Files' and try to open it on Chrome or Brave, all the inputs appear to be disabled, but when I refresh (or enter online mode again), they return to be available.
Is there a work around to this?. I want to build an offline web-app, but it seems that forms can't be incorporated.
I tried to test this error in dev tools using my computer, since there is an option to emulate being disconnected from the internet. But the doesn't go very far, since the website only appears with 'No internet' and not really with the offline view that I get from my cellphone.
I created a PWA with Blazor WebAssembly straight out from the template in the latest Visual Studio 2019. Most of the app is working great and I managed to add the app to my home screen on an Android phone.
My issue now however is that whenever I swipe down/refresh on any page I get the ERR_FAILED page, this is consistent. Always when I swipe down to refresh it gives me this error. The same error happens with an obviously valid URL (same URL was just loaded) when I press F5 in Chrome for the PWA. I get the ERR_FAILED. Any idea what is causing this? The navigation in the app works great otherwise. The app is hosted in a subapp in IIS called "wapp". I am using localStorage to store user data.
ERR_FAILED
On a web application we manage, there is an issue only present in Edge Chromium. There is a button to download a file: an Excel macro file. When clicking the button in Edge, the file is opened in Excel. However, the login page of the webapplication appears in the XLSM file in Excel, instead of opening the xlsm file itself. In Google Chrome, the file is not opened, but downloaded first and when clicking open, we get the wanted behaviour.
This is the code behind the button (confidential data replaced by XXX):
<input type="submit" onclick="redirectToNavUrlGA('https://XXX.xlsm','XXX','XXX','XXXXXX'); return false;" value="XXXXXX">
When calling the URL directly in a cache cleared-Edge browser, the login page appears in browser and the file is downloaded correctly. Only when you are already logged in the to application, the issue is present. But users will always be logged in already, so not a good workaround.
The URL is using reverse proxy to point to a Sharepoint 2010 site to download the file. I've read some issues with Edge Chromium and SP 2010, is this maybe the cause of the issue?
Do you have any other ideas that could be causing this issue?
Thanks in advance.
According to your description, I think the main problem is the compatibility issue between SharePoint 2010 and Edge. The Edge browser is not included in SharePoint 2010 browser support, and even Edge IE 11 mode is not supported. So I suggest that you can use a supported browser.
When using the Microsoft Edge browser, by default when you open a PDF it will open the PDF in a new tab using the built-in PDF viewer. To avoid this, you can adjust the browser's settings: Toggle on the "Always open PDF files externally" option. This works great. However, it presents a separate issue. Our internal applications use embedded PDFs in iframes. When the external toggle is set to on, these PDFs will not show in the iframes. This doesn't happen in Chrome. Has anyone else experienced this and know a work around?
I've tried removing the type="application/pdf" from the iframe tag to no avail. I can't find anything else online.
It looks like an expected result because you have enabled the option Always open PDF files externally.
So MS Edge browser is giving you an option to download the PDF file and open it using the desired app.
You said this doesn't happen in Chrome browser.
If you enabled the Download PDF files instead of automatically opening them in Chrome option then you will notice the same result in the Chrome browser.
Output in the Chrome browser:
If you click on the Open button then it will download the PDF file.
I did not get any solution or a workaround for this issue.
If you think that there should be an option to load the file in an iframe if Always open PDF files externally option is enabled then I suggest you click on the Send Feedback button in the MS Edge browser and try to provide your feedback about it to the Microsoft.
I posted feedback suggesting that an exclusion/inclusion list be in included but the simplest way would be to treat the frame as part of the session. But this is not Microsoft it is the Chrome projects issue.
In Chrome, I have the WebGL Inspector extension installed. The debug option does not show up in the address bar for the page I'm working on (that I'm using WebGL in). It shows up for other pages on the web. What are the requirements for getting it to give me the debug option?
I guess that you are trying to debug a local file (file://). If so, navigate to chrome://settings/extensions, expand the WebGL Inspector item and check "Allow access to file URLs".
Note: (outdated?) "readme.md" says:
You cannot inspect pages on file:// in WebKit (possible with security settings?)
You can also install a web server on your local PC to dispatch your page from a http:// url.