I try to execute an SQL query with Chrome DevTools for an Android app, but it's not possible, because enter button moves the cursor to the next line instead of executing a commend. It worked some time ago.
I reinstalled Chrome, removed all Chrome data and reinstalled, used Chromium browser, but still no result.
All the other functions of DevTools are working correctly, e.g. networking, database preview.
It's happening with different apps and devices.
Could anyone help?
This is a bug in new versions of Chrome. So far, the only workaround I found is to download an earlier version, 71, for example from here:
https://www.slimjet.com/chrome/google-chrome-old-version.php
You can look here for a detailed discussion:
https://github.com/facebook/stetho/issues/634
Related
I have been working on a simple portfolio for myself and have it deployed to an app on heroku. I have used the typical commands to add, commit, and push to GitHub and everything is updating normally there.
My issue is that when I open the app from Heroku in Chrome, it is not displaying the recent updates. When I open the link on my phone, it looks correct according to my HTML and CSS code. I have tried both automatic and manual deploy methods, but I still cannot get Chrome to display any of my updates.
Has anybody experienced this? I'm including screenshots below.
How it displays in Chrome
How it displays in Mobile Safari
Chrome sometime uses previously cache data of website to load website faster unlike safari, try using incognito mode or another pc or even a smartphone. There is also a service called browserling where you can test out on different browsers.
I'm using vidyo.io as videoconference solution in our platform. I'm having an issue with Vidyo's Chrome extension for screen sharing that is easily reproducible using the very own Vidyo's samples:
If you download Vidyo's web sample from developer portal, open samples/VidyoConnector/js/VidyoConnector.html in Chrome, choose 'Join via the browser', and click the 'Window share' select list (there is no need to start a conference to reproduce the error), Chrome will open the Vidyo Screen Share extension page twice, even if you already have the plugin installed. For this to work you have to uninstall the extension and reinstall it again. It will work until the end of the current session.
In the other hand if you go to Vidyo.io developer portal, choose "Demo" from "Developers" menu and start a conference using the "Join via the browser" button, click the same 'Window share' select list the Vidyo Screen Share extension works as expected, allowing you to pick a window or a screen to share.
In our implementation we're having the same problem as the code from web sample listed above, but if an example of our code would be of any help to clarify the issue, here you have an excerpt (we're using Angular, and here you have some TypeScript code):
private vidyoConnector: VidyoClientLib.VidyoClient.VidyoConnector;
(...)
selectedWindowShare(share: VidyoClientLib.VidyoClient.VidyoLocalWindowShare) {
this.vidyoConnector.SelectLocalWindowShare({localWindowShare: share})
}
This issue happens only on Chrome. When we use Firefox it works seamlessly. I'm using Chrome 69 on OSX High Sierra.
Any suggestion on how to solve this will be much appreciated. Thanks in advance!
If I am not mistaken, you are either running the VidyoConnector.html directly in the browser or hosting the sample on non-secured hosting (HTTP).
For the Vidyo Screen Share Chrome extension to work correctly, you need to host it on a secured hosting (HTTPS).
You can verify this by using our hosted sample here:
https://static.vidyo.io/latest/connector/VidyoConnector.html
Hope this helps.
I've been using Chrome forever for development, but it seems as if the last few versions - they've changed the functionally of the Web Inspector.
For instance, before I was able to search the 'Resources' tab, but now I have to search via the console, which makes it less easier than the way before I think Chrome 31.
Is there a way to rever back to the previous Web Inspector?
Same thing with Safari, but they changed their Web Inspector long before...
Thanks,
Roc.
Is it possible to make a Chrome app handle certain types of extensions?
For example, setting a Chrome app to be launched when you double click a .txt file, instead of launching the Chrome app first and browsing for the file.
Yes, on ChromeOS via file_handlers. On other operating systems, not yet.
The bug to track this work on Windows: https://crbug.com/130455
Linux: https://crbug.com/138665
I'm not sure if / where there is a mac bug but it is also planned.
This should help you : http://www.computerhope.com/issues/ch000128.htm
Especially the part at the end of it.
In the future - Google it, it was like the 2 result.
Until recently, when paused in Chrome debugger on a breakpoint, the current state of a JavaScript variable, array or object would pop up in a yellow dialog if hovered over with a mouse. That is no longer working though I'm at a loss to know what has changed. Has anyone else experienced this? It's really making debugging a lot more difficult on this computer. My other computer still has the normal behavior in Chrome Dev Tools (both Windows 7 machines). Thanks in advance.
The same thing happened to me on 16/12/19, with version 79. But in Chrome canary, it is working fine. People who need can download it here (you can use it for now) or you can use Chrome Dev here
For the people who don't know about Chrome Canary or Dev
Chrome Canary is an experimental version of the popular Chrome browser. Google offers four release channels for its Chrome browser: Stable, Beta, Dev, and Canary. Most people use the Stable release of Chrome, which is rigorously tested and considered very reliable.
By contrast, Chrome Canary may appeal to people who like noodling around with new technology and want to get an advance look at what the standard Chrome browser may look like in the future.
Updated my chrome to version 79.0.3945.117 (Official Build) (64-bit). popup after hovering to variable is not showing.
Luckily, I found solution on google(don't know about the source now). Simply turn off the
Hardware acceleration feature and it worked. If you ignore impact of hardware acceleration turn off, this is the ideal one.
Canary version 81>= is another solution for this feature to work.
This was resolved in a later version of Chrome and is no longer an issue.