I'm building a chrome extension in ReactJS and I've integrated react-paypal-button-v2 button.
It works well on windows chrome browser but issues in MacOS Catalina, when we close the payment window popup, it also closes the extension popup. hence we can't detect payment callback functions like onSuccess() to determine success or failure.
Related
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.
Using window.open to open a new window in chrome the device icon in the dev tools is not present.
window.open('https://google.com/', '_blank');
I feel like this is a bug in Chrome as I'm not sure why they would want to prevent it? Or am I missing a way?
I saw another question but the bug that was logged was about network throttling not allowing device tool available. How to toggle Device Mode on a popup window in Chrome?
I'm assuming this is a bug and have opened an issue
Is it possible to create a Chrome shortcut that will launch a web app in such a way that users will not be able to view or access the URL of the web app via Chrome, e.g., via the address bar, status bar, developer tools, etc. If not, would it be possible if I packaged the web app as a Chrome app? I should note that I am not concerned about the shortcut itself containing the URL, e.g., in its "Properties", because I already have an executable will which launch the shortcut. All I care about is the user not being able to view the app from within Chrome itself once the app has been launched, at least not easily.
I have tried adding Chrome flags/switches, namely, kiosk mode, fullscreen mode, and app mode, but none of them work 100% as needed. Kiosk and fullscreen modes will launch as such only if no other instances of Chrome are open; if another instance of Chrome is already open, both modes will launch in a regular view mode in which users can see the URL in the address bar. App mode (I added "--app=http://www.example.com" to the end of the "Target" property of the shortcut) is promising because it launches with no browser chrome, but I notice that if I refresh the page while in app mode, I can see the URL both in the top window bar and the bottom-left status bar. Also, app mode doesn't prevent the user from opening Developer Tools, which makes viewing the URL trivial.
Any ideas welcome!
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.
I'm developing a chrome app. Whenever I restart the app to test new code (from context menu or chrome://extensions), the developer tools window closes and I have to re-open it manually (right click > inspect element). Previous behaviour was that the developer window would also automatically re-open during this process.
Right now I'm trying to actually debug code that runs on app load, and I can't get to any break points because by the time I can manually re-launch the developer tools they've been missed.
How can I have the developer window automatically re-open when the app is restarted?
No.
You can't programmatically open the Chrome DevTools.
What I suggest is to change onload to a function, and call that from the console.