Bug on hover in chrome debugger? (v79.0.3945.79) - react-native

I'm debugging a React Native 0.61.5 app with Chrome and usually when code stop running on a breakpoint and I hover a property, I can see all the details of it in a popup window. But for two days now I can't get back this functionality. I restarted computer, cleaned Chrome and Metro bundler, tried with virtual or real device but it's still not working. Did I deactivated something accidentally ?

Update:
The issue seems to be resolved with the new Chrome update 79.0.3945.117.
Yes, with Chrome 79 this functionality was broken. This is the thread where people are reporting this bug:
https://support.google.com/chrome/thread/22882968?hl=en
(and also in the link from the comment to this question)
And this is a thread where Chrome developers are tracking this issue and trying to fix it:
https://bugs.chromium.org/p/chromium/issues/detail?id=1033022
In Chrome Canary (81) this feature is working, and it's reportedly working in the Chrome Dev version (80). Other alternatives are Firefox (also people say that it's working in Opera and other browsers) and debugging via VSCode.
It seems they aren't going to fix it until the version 80, which isn't expected to be released until February (from what people say in that thread: https://support.google.com/chrome/thread/22882968?hl=en).
Also there was this change: https://chromium-review.googlesource.com/c/chromium/src/%2B/1835357
which made variables appear on hover only inside the innermost scope. Update: this feature (to evaluate outside the innermost scope) will probably be restored:
(from https://bugs.chromium.org/p/chromium/issues/detail?id=1033022)
"This undoes
http://chromium-review.googlesource.com/c/chromium/src/+/1835357,
which limited the eager popover evaluation to the innermost scope, which
is the only scope for which we can produce reliable results right now.
For the outer scopes, it might still produce the right results, but we
can't guarantee that. But the feature is still very useful and so we are
restoring the behavior here, and will follow up with a proper fix and UX
later".

Even with last Google Chrome update I was not able to resolve this issue. The issue comes from the Chromium version of Google Chrome.
You need the version 81 of Chromium who fixes the bug.
I downloaded the last Chromium browser with Chromium 81 and it's working for me https://chromium.woolyss.com/download/fr/

Related

Selenium for Chrome version 103 is just crashing, I know it's not my code because whilst its still crashing at one time it still ran

The script is crashing on Chrome version 103 only it's still running on 102. In one instance, it ran but crashed while executing a loop for its fifth time. It is selenium + python. What should I do?
this issue came with chrome 103. Remove the user-data-dir option for solution.
It was fixed for me when I removed the user-data-dir option.
It looks like this problem will go away when chrome 104 is released, we'll be dealing with workarounds until chrome 104 comes out.
https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121
https://github.com/SeleniumHQ/selenium/issues/10799
New Answer
Chrome Version 103.0.5060.134, selenium is now working as normal
Old answer
I actually:
Uninstalled Google Chrome
Restarted the computer
Installed an older version of Chrome(whilst the Internet is OFF)
Run MS config & disable Chrome auto-update
Restart the computer.
Now it runs just FINE.
NB: This can make your computer vulnerable to attacks so don't use your main PC. Use Isolated Environments
.

IntelliJ Idea Ultimate cannot enter debugging mode

When I try to debug it shows this dialog:
Error dialog
And when I clock "fix" It shows this:
Web Browsers dialog
I can't solve this problem, any suggestion? Also I am developing a react native app. But i don't think that's the problem...
I am running Intellij Idea in Elementary OS.
This is expected - debugging is only supported in Chrome and browsers of the Chrome family, as it's clearly stated in Help. So, when you start the debugger, the IDE will try to open Chrome regardless of the browser chosen in run configuration. You need to make sure that Chrome is installed and the correct path to it is specified in Settings | Tools | Web Browsers.
We used to support Firefox Remote Debugging (but without source maps) through the FireFox Remote run configuration, but our solution doesn't work in the latest Firefox versions due to changes in the protocol, and there doesn't seem to be an easy way to fix it. We've made some progress recently, but there are still some blocking issues
related ticket: WEB-45986

Selenium tests broken by recent update of safari to version 13?

does anybody have a problem of selenium tests failing on new safari version 13.
Ran the same tests on chrome and firefox and it works fine. Also tested it on older version of safari and it works fine.
I didn't manage to pin point exactly where it fails. One case I did notice is that on safari 13 selenium click on <div role='button' aria-haspopup='true'>....</div> invokes no action(in my case opens a popup menu). And test proceeds to the next line of code. note however at this point I am not claiming that this kind of click always fails, it's just where I noticed it in my tests.
If anyone came across this kind of issue on safari 13 please provide your input.
Thanks
Safaridriver maintainer here.
This is a known issue that we believe has already been fixed in Safari Technology Preview Release 91. Please verify whether the issue reproduces using latest STP's safaridriver, and reach out to me on Twitter, #brrian.
There is an issue with SafarDriver or Safari 13. Please vote the bug in WebKit https://bugs.webkit.org/show_bug.cgi?id=202589
I am also facing the same issue with Safari 13.0 and Safari 13.0.1. Till Safari 12.1.2 everything was working as expected but since my browser updated to v13.0 selenium script is broken.
I observed that Selenium clicks on other locator instead of the target (identified) locator. For ex. if you want to click on a button (//button) it clicks on the //div which is the sibling node of that //button in the DOM.
My workaround solution:
As I didn't update MacOS Catalina yet and only Safari 13 was updated; I was able to download the "MacOS Mojave installer". Then, I installed it as an update; resulting it rolled back my Safari version from 13.0 to Safari 12.1.2. Now my script started working again!!

Selenium Webdriver for Chrome Crashing vb.net

I have a program that has been working for quite a while. Not sure what happened, but all of the sudden it crashes. It looks like it is trying to access something on the page when this happens. It launches Chrome, gets to a login page, but then it crashes when trying to grab the login. Happens with multiple sites, so it isn't a site change or anything like that.
I tried converting to Firefox and InternetExplorer. However, because Chrome lets you download a file without prompting, that is what I know will work. I tried with FF creating a Profile and with IE creating a registry setting (to allow auto-download). Neither worked :(
I want to go back to Chrome, but not sure what is wrong. I even uninstalled Chrome entirely and re-installed it. Nothing :( I tried setting ChromeDriver.exe to "Run as Administrator" - nothing crashed, but also nothing ran.
I'm at a loss :(
the latest version of chrome has a rendering bug which is causing errors when working with selenium, you can try installing the latest chromedriver but it might be better to try to find a work around with firefox for now

What happened to Opera Dragonfly?

Using either 20.0.1387.82 or 22.0.1457.0 (developer)
When I right-click and select Inspect Element, I get a vanilla Developer Tools dialogue:
not the one always pictured:
It looks identical to Chrome's debugger (though I've uninstalled Chrome), most notably absent, the icons on top row and the remote debug facility.
Anyone know how I can get Dragonfly working on my machine?
Opera ditched their Presto rendering engine and built a new browser (also called Opera) around Blink (Google's fork of Webkit). It doesn't support Dragonfly any more.
There are plans to port it to the new browser.