For some time now, I'm not able to use the "copy as curl command" anymore. It's just an empty context menu, please see attached screenshot. Anyone else experienced the same issue?
I'm running chrome 90.0.4430.30 on a mac
Seems to be working fine for me on version 89.0.4389.90. I'm guessing that since version 90 is relatively new it has some bugs. Perhaps try downgrading back to the previous version or try reaching out to Google Support.
Related
I am new to coding.Have got a few line of code i am working on and anytime time i try to open it with a live server i encounter a problem as shown in the image. I have tried to solve the issue with by looking it up on Google but could not. I need you all to come to my rescue as soon as possible. Thanks
I expected the code to run smoothly on live server but it would not.
I use Chromium on Ubuntu and I see an error "The server encountered an error. Please try to reload the page" in loop when I try to access websites like grammarly.com, slack.com. I have also tried to access it on Chrome, Firefox but results were same.
I have also done numerous self-diagnostic tests which was recommended by Grammarly-Support, but nothing seems worth doing. Here is the test result:
Here is the console result:
It's been a year, and since then I've been facing this problem. Please help me to understand what is wrong. Any suggestion on this would be highly appreciated.
I've just observed a strange behaviour of app.grammarly.com.
In Firefox, when I'd disabled the following in proxy-setting:
FTP Proxy : Null
SOCKS Host : Null
I am able to access the app.grammarly.com successfully.
I get the same problem with Windows 10 and Chrome. I also contacted Grammerly and they said it was a connection issue at my end, second time they said it was my internet provider.
I find that it happens when I have multiple tabs open in Chrome. Closing most of the tabs and refreshing the page with Grammerly fixes the issue for me.
Hope this helps to find your solution.
-Tina
I used "chrome://inspect" for a few days. Everything was fine. Today, for some reason, when I click "inspect" the result is "404 Not Found The resource could not be found."
What could be the reason for this ?
I was able to find only this topic: https://code.google.com/p/chromium/issues/detail?id=329979
I guess the drivers are OK if the device appears ? I`m able to transfer files, to "focus tab" or "close tab" and "reload" but i can't "inspect".
Chrome Version: 37.0.2062.124 m
DevTools URL : chrome-devtools://devtools/remote/serve_rev/#180870/devtools.html?&remoteFrontend=true&dockSide=undocked&toolbarColor=rgba(230,230,230,1)&textColor=rgba(0,0,0,1)
Edit:
I tink this comment is important so...
A bug was opened in the Google tracker: Link Please star it! Remember that you don't have to add a comment to it if you don't have new information :)
by MM
Edit 2:
DevTools are actually broken for ANY kind of Android devices, regardless device's version, Chrome version or OS. URLs of such kinds - http://chrome-devtools-frontend.appspot.com/serve_rev/#180870/devtools.html - that must return DevTools code - now returns 404. That could be fixed by Google without any change in the Chrome code, it's completely server-side problem.
by vrid...#gmail.com at bug tracker
Edit 3: At this time http://chrome-devtools-frontend.appspot.com/serve_rev/#180870/devtools.html is OK but slow. I realy cant get why I need usb driver to send data over the internet... to this page just to debug.
I had the same problem, but it was caused by chosen AOSP WebView instead of Chrome Stable at Developer Options > WebView Implementation. If you do not have Chrome Stable option available, then try to install Chrome and check again.
Just had the same issue. VPN was on, turnning it off fixed it.
That was a cloud storage glitch. Things have reverted to normal since then.
After updating chrome version on Android device worked for me.
This still occurs and workaround is to open chrome://inspect and click on inspect link under Remote target assuming the command node --inspect server.js is already hit.
Workaround:
disable chrome updates. Instructions: https://www.makeuseof.com/tag/stop-automatic-chrome-updates-windows/
uninstall latest Chrome on desktop.
install previous version: (I used slimjet: https://www.slimjet.com/chrome/google-chrome-old-version.php)
Open chrome://inspect/#devices url and choose inspect-fallback instead of inspect.
Please refer to the link to see what kind of screenshots I get - http://goo.gl/uDIyf3 instead of http://goo.gl/BQy1hI .
Not sure what could be wrong here as the same code has been working for me on other machines. The only possibility that I see is an issue with the configuration on the machine but can't find what that issue is.
The same scripts when ran in IE, it renders the correct screenshot, so it could be a chrome specific issue. Have uninstalled & reinstalled chrome but still the same.
I am using Selenium 2.28.0 version.
Please let me know if anyone needs more inputs my issue. Any hint to resolve this would be really helpful.
Have posted the same question on sqa as well - https://sqa.stackexchange.com/questions/9535/blurred-screenshots-with-selenium-webdriver
Thanks
I'm seeing this problem too. Here's the method that takes the snapshot. The same code works on IE9 but produces the mirrored screenshot on Chrome.
def screenSnapshot(self):
try:
if self.__snapshot_dir:
self.__WD.get_screenshot_as_file(os.path.join(
self.__snapshot_dir,
"screenshot-{}.png".format(time.strftime("%Y%m%d-%H%M%S"))))
return(True)
except Exception as e:
print("Exception: {}".format(str(e)))
return(False)
I'm using a remote webdriver. The node is running Windows 7 Enterprise with Service Pack 1 installed.
Any other suggestions I could try? I have the latest Chrome driver too.
I'm trying to automate packaging of the Chrome extension on Windows and according to the documentation, it is this command:
[path]\chrome.exe --pack-extension=c:\myext --pack-extension-key=c:\myext.pem --no-message-box
However this command results in a new browser window and no action is performed. I tried other switches like --version or --help but it seems that Chrome is ignoring all of this. Do others have the same issue? What am I doing wrong? I also tried various quoting and with no other browser window open but I haven't been able to make this work.
Update: I'm happy to learn that the new Chrome 8 has fixed this issue.
The answer is present in one of the comments. I am reposting the answer verbatim here:
You can try one of the scripts to pack
an extension at
https://developer.chrome.com/extensions/crx#scripts
– by Na7coldwater
You'll need to close all chrome windows before the command line pack extension command will work.
I raised this bug with the chrome team some time ago (http://code.google.com/p/chromium/issues/detail?id=22901) but it's not quite fixed yet. This can be somewhat frustrating because (as michaelhermannweber pointed out) "Since we're fans of Chrome, obviously Chrome is already open!"
I even tried to use a separate instance of the chrome executable to build the extension, but alas no luck on that front either :(
For now, AFAICT you have to do it manually via the pack extension button on the chrome://extensions page.
You might manage to build a script that closes all open chrome windows, builds the extension, and then re-opens chrome. But I doubt that it would be worth it given the number of tab users like to keep open.