Click Once applications not launching in Chrome - google-chrome

I have a web application which supports two click once applications. The web application works well under IE11 and both click once application launch under IE11. However I was recently trying to get my web application to operate under Chrome version 65. I installed the following ClickOnce extension under Chrome:
Meta4 ClickOnce Launcher
Now the above extension would not launch the supporting Click Once application in Chrome. The Click Once applications were developed in VS 2010.
I use php to call the Click Once application
header( 'Location: http://sanplic02.corp.mycompany.com/LaunchCatia/LaunchCatiaPWBSTART.application?licence=DP2&computername='.DisplayComputerName());
Does anybody have any ideas as to why this is so.
Any help much appreciated.

Now I eventually got my web application to work in Chrome. All of the above is correct. The extension I used was the Meta4 Click Once Launcher. The line of php code above is also correct this is how I launch the click once application supported by the web application.
So what was the underlying problem. Well essentially I was disabling my submit buttons in code. Even though the submit buttons were programmatically disabled they operated correctly under IE11 another words the submit buttons appeared enabled in IE11. However in chrome on the other hand they were disabled, hence Chrome would not execute the script that launched the click once application script. So once I removed the code to disable the submit button all went well.
The joys of cross browser compatibility.

Related

Why are my offline web-app inputs not working?

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.

How to open javascript developer console from SAP HTML Viewer

We have a custom web application that gets used via normal desktop browser, including IE, Chrome, and Firefox. When troubleshooting javascript type issues with this application, we can use the F12 button to open the javascript developer console.
This web application is also referenced inside of SAP GUI via the HTML Viewer.
The trouble that we have is that clicking F12 does not open the javascript developer console for us. Does anyone know how we go about opening this javascript developer console for a web application within SAP GUI HTML Viewer?
If you're using newer versions of windows, you might want to give F12Chooser.exe a try. It's the same developer console you would get from hitting F12 on IE, but it gives you the ability to choose a target to debug.
You can find the exe at C:\Windows\SysWOW64\F12\F12Chooser.exe (change SysWOW64 by System32 if you're on a 32bit machine)

IT Hit WebDAV AJAX Library on Chrome becomes unresponsive

I am experiencing an issue with opening a Microsoft Office Document, using IT Hit WebDAV AJAX library, in latest Chrome 39.0. running on Windows OS. It is a sporadic issue that occurs only in Chrome, and it happens when one opens a document multiple times. Word instance won't start, the page freezes and browser becomes unresponsive, and Chrome suggests killing the page. The only solution is restarting the browser, which solves the issue.
I have tried opening a document in Chrome on Mac OS X, and it is working fine. So are Mozilla and Safari on all operating systems. It seems to be a Chrome + Windows issue only.
Has anyone experienced this issue and is there a fix?
The Microsoft Office plug-in that opens the document displays a warning popup "Some files can harm your computer.", which is a modeless dialog:
If you quickly click on a link that opens the document more than one time the dialog will hide behind the main web browser window. As a result the web browser window is blocked.
You need to switch to that dialog and confirm or reject document opening, otherwise after some time Chrome will ask you if to kill the page or wait.
Note that there is no way to avoid that dialog, this is a built-in MS Office functionality as far as I know.
Chrome will only work good with ITHitWebDAV if the user has got Office 2013 or superior.
Google is blocking all Java applets and NPAPIs now, so good luck with that. I just detect the browser of the user that wants to edit a document, and if it's chrome, I warn him to change to another browser like Firefox with a modal, and that's all.
Very poor support between Chrome and ITHitWebDAV, and no much you can do about it.

Chrome 32 - Tab opened with chrome extension doesn't render plug-in correctly

We have a Chrome extension that can be used to open a page into our website. From there the user then continues onto the next page which has a custom NPAPI plug-in embedded in it. This has always worked fine. However, since the version 32 update the plug-in loads and runs (it's a video conferencing plug-in and is clearly running as the other side can see video) however it doesn't show up on the page. Examining the DOM everything looks fine. Grabbing the border and re-sizing the browser will cause the plug-in to suddenly render correctly. I've tried all manner of javascript/css tricks to try and mimic this behavior as a workaround but nothing works. Tabs opened manually (not using chrome.tabs.create) work fine.
This worked up till 32.
Any ideas around this?
Chrome 32 is phasing out NPAPI, read the announcement here.
There is a deprecation guide that you can read here.
It seems like Google wants you to use it's Native Client tech to run native compiled code on user's machines. It is cool stuff...but so far I've found it difficult/more limiting to work with when compared to NPAPI (but there are obvious upsides, security for instance).
You could also build a native app and use native message passing to communicate from extension -> app. Once downside to this is that there is currently no way to bundle a native app into an extension install, so the user will need to download and install your app separately.

Does Google Chrome Frame break IE8 console output?

This is a question about debugging a project, not about writing the code.
I am on the final stages of developing an HTML5 web app. Fairly last minute, our client tells us it should run on IE8. Since I use the HTML5-canvas in the app, this required the addition of Google Chrome Frame. Once installed and testing, however, IE8's developer console no longer prints any data, and the HTML viewer never loads. Is this a bug? Is there a way to fix it? It will really suck if I need to debug with alerts...
From Google Chrome Frame documentation:
You can use the Web Inspector in GCF just as you would in the Google Chrome browser. To use it, right-click and choose "Inspect Element". Logging is available via the console.log method, and you can set breakpoints and inspect network activity.