I'm trying to use SDK Inspect tool to set value in the address bar of Opera but it keep getting error:
Value.SetValue
Called with parameters:
val: abcd.com
Result:
ERROR - [Error: hr=0x80004005 - Unspecified error]
I can set value it with Firefox and Other Chromium browser but not Opera. Does Opera has something prevent other process access its UI and how can I bypass it ?
Related
Folks,
I am trying work on a simple Web MIDI app.
I already looked up and found out that Google Chrome is the only browser that supports this. So, I installed this but I still get this.
WebMidi could not be enabled Error: The Web MIDI API is not supported
by your browser.
at WebMidi.enable (webmidi.min.js:30)
at script.js:430 (anonymous) # script.js:432 WebMidi.enable # webmidi.min.js:30 (anonymous) # script.js:430
Promise.then (async) (anonymous) # script.js:154
Mac - 10.15.2
Chrome - 79.0.3945.117
According to this link - https://www.midi.org/17-the-mma/99-web-midi , Chrome definitely has the support.
Important Note - If I were run the code directly on codepen, it works just fine. So the browser is working. But when I try to run locally, I get the error.
https://codepen.io/teropa/pen/JLjXGK
WebMidi.enable(err => {
if (err) {
console.error('WebMidi could not be enabled', err);
return;
}
What am I missing here? is this a chrome issue or Mac issue or some permission issue. Or, is there is something specific I need to make the MIDI code run locally?
I am using this server, https://www.npmjs.com/package/http-server, to run the code locally.
(I have looked at other questions but did not find anything that relates to Chrome on Mac)
I've used web-midi with Chromium and Opera on 10.12.6, so I wouldn't say that Chrome is the only browser that has web-midi.
With Opera I think I had to enable experimental features:
chrome://flags/#enable-experimental-web-platform-features
Maybe see if Chrome needs that too?
Or maybe it's just a side-effect of all the lock-down in 10.15?
if serving dev site from 0.0.0.0 you won't get any MIDI in browser, but when loading from 127.0.0.1 it should work ( as commented by user Alex above )
I am trying to debug react-native app running on VS emulator in chrome. The error I am getting at the moment is "Cannot set property 'volume' of null". It is like 4th or 5th cryptic error I am getting since starting, but the first one when I hit the wall. I will outline all configuration steps in case I botched something earlier:
Initialized project with react-native init myapp
Started the bundle server with react-native start --host 192.168.100.4 (the reason for host parameter is CORS error)
Started the app with "react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res && react-native run-android" (the reason for react-native bundle command is assets error)
On emulator went to shake -> Dev Settings -> Debug server host & port for device, set it to 192.168.100.4:8081 (the reason for that is "cannot connect to bundle server on localhost)
shake -> Debug JS Remotely
Chrome window opens, I hit F12. Now it still displays CORS error for a while, but after some page refreshes it displays "Cannot set property 'volume' of null" and sticks to it:
(index):94 Uncaught TypeError: Cannot set property 'volume' of null
at Object.render ((index):94)
at Object.setState ((index):48)
at WebSocket.ws.onopen ((index):152)
Just in case, here is CORS error that I get initially:
Failed to load
http://localhost:8081/index.delta?platform=android&dev=true&minify=false:
No 'Access-Control-Allow-Origin' header is present on the requested
resource. Origin 'http://192.168.100.4:8081' is therefore not allowed
access. If an opaque response serves your needs, set the request's
mode to 'no-cors' to fetch the resource with CORS disabled.
(index):188 Uncaught (in promise) TypeError: Failed to fetch
It goes away after page refresh, but I wonder why it still happening.
Did anyone manage to setup Chrome Debugging with VS emulator and react-native? If so, please share your experience, all tutorials I found just happily advice to run react-native start and react-native run-android and everything should be smooth ride after that )
I had a similar issue with the debugger mode and was getting an error.
I am not sure of the WHY? to that answer but the extensions in the chrome might be the problems. I disabled the extensions and I didn't get any of the errors post that.
Open the application
Select DevSettings
Choose Debug server host & port for device.
Type your system ip address along with the port number of the metro
builder.
For getting system ip address.
Open command prompt
Type ipconfig
Select ipv4 address
I am trying to launch a test case using Chrome headless. I authenticate with this line of code:
WebUI.authenticate("url", "name", "password", 10)
but it gives the error: Unable to navigate to authenticated page (Root cause: java.lang.Exception: Unsupported browser (only support IE, FF, Chrome))
There is a similar problem on the Katalon Forums. There is a proposed workaround (for an example url of https://dev.mcdonalds.konoss.net/):
WebUI.openBrowser('https://Username:Password#dev.mcdonalds.konoss.net/')
Try with FailureHandling
WebUI.authenticate("url", "name", "password", 10, , FailureHandling.OPTIONAL)
I am implementing a functionality where am referring core.ashx file which works for IE but it gives an error 'Refused to set unsafe header "Connection"' in google chrome.
below are the console log error details.
ajaxpro\core.ashx
if(!MS.Browser.isIE) {
this.xmlHttp.setRequestHeader("Connection", "close"); // Mozilla Bug #246651
I followed some articles which are highlighting about security concerns related chrome browser and hence "xmlHttp.setRequestHeader" will not run in chrome browser.
Any help is appreciated.
-Shrivallabh Davalbhakt
I have some canvas code that works great in safari and chrome, but fails in firefox.
The firefox console reads:
[17:44:13.372] uncaught exception: [Exception... "Operation is not supported" code: "9" nsresult: "0x80530009 (NotSupportedError)" location: "http://REDACTED.js Line: 703"]
Firebug gives the slightly-more-useful-to-humans:
Operation is not supported
var data = ctx.getImageData(x,y,1,1);
I am indeed calling .getImageData on line 703.
I have read that similar errors have been reported with regards to origin policies. This project is hosted on a web server (not local), and I haven't loaded any images from a different domain and put them on the canvas. In fact, I get the error even if the canvas is blank.
The webkit-based browsers give me the pixel data as asked, what can be done about firefox? Thanks.
Don't pass NaN to .getImageData.