I added an extra parameter to Chrome "--disable-web-security". After I add this the "same origin policy" gets disabled which is exactly what I want.
The problem is that when I start Chrome an yellow information bar appears at the top and says:
"You are using and unsupported command-line flag: --disable-web-security. Stability and security will suffer."
The weird thing is that the flag seems to be supported as I tested Chrome with and without it.
My question is: Can that information bar be disabled with another flag or any other way ?
Thanks in advance
Try going to about:flags in the address bar and disabling Native Client..
Related
Since yesterday I have following problem: The variables in session storage are not visible anymore in chrome/devtools under session storage. In the console, I can call the variables, so they're here, but not visible.
So far the only way I could solve this problem is by changing my chrome profile to "gast". Then I can see the variable back. But I don't know which settings should I do to make it work under my regular profile.
Anyone a clue?
I had the same problem and I just solved and it was very simple.
1 - Open devTools and go to Settings
2 - In Preferences roll to the bottom of the page and select the "Restore defaults and reload" option.
I'm seeing the same thing, the localStorage preview sometimes gets stuck and is not updating. Reload or reset of preferences is not helping.
Reported it here: https://bugs.chromium.org/p/chromium/issues/detail?id=1414104
Had the same issue.
My teammates could see data in the application tab, but I could not.
What solved the problem was running:
chrome://restart
in the address bar.
Hope this helps.
I've written an application(webrtc screen sharing), everything is ok with chrome.desktopCapture.chooseDesktopMedia if you pick another window to share but if you pick chrome window(self) to share it gives you just empty stream.
No error just nothing. Is this a known bug? Or any solution this? Is there any way to disband chrome window from windows list at least?
Edit: hardware acceleration enabling/disabling doesn't solve the problem.
You can't disable a single application to be listed in the windows list. You can disable the whole option. This would mean you won't be able to share any application.
You can customize this when calling chrome.desktopCapture.chooseDesktopMedia, sending the set of desktop media sources you will allow to select when sharing:
"screen", "window", "tab", or "audio"
Check this link for more details.
If you could provide some code on how are you using Chrome API to share the screen that would be great to be able to provide more details on how you can solve your issue.
I have recently started to see a frequent error in Chrome Dev Tools when right clicking on an element for the purposes of selecting "Inspect Element" - instead of selecting the element on the "Elements" tab the error "Uncaught Error: Parameter 2 (message) is required." appears in the "Sources" tab for a virtual "extensions:: schemaUtils" script.
The error occurs in the function "validate" as per the screenshot below.
This error seems to occur since installing the "OneTab" extension, and indeed goes away when I disable it. I have reported it to the extension author, so far without response. Unfortunately as work have seen fit to issue me with an underpowered machine, removing OneTab is not an option as memory otherwise runs in extremely short supply.
The issue is easy to replicate, within Stack Overflow itself click on the "StackExchange" icon top left, and then right click on one of the "Your Communities" items. The context menu does not open and the above error appears. This also affects the pop-out menus on the primary product I am working on.
This error only occurs in a single instance of Chrome, which happens to be my primary developer machine, and does not occur on Chrome Canary on the same computer, and with the same extension installed.
Chrome 37.0.2024.2m on a Windows 7 Professional, Service Pack 1, x64 laptop.
Do I have a corrupted copy of Chrome? Can other users replicate this error (with or without the OneTab extension)? Is there anything short of removing the extension permanently that I can do to restore essential "Inspect Element" functionality?
I have already tried resetting Chrome within the settings menu.
The problem you're experiencing is that a breakpoint is triggered for (uncaught) errors.
To stop this from happening, open the Sources tab of the developer tools, and make sure that the circle with the two stripes in it is GREY, not blue. This circle means "Pause on exception" and is the right-most icon in the next picture.
Just stating more clearly : if you are ok with that, just disable the OneTab Chrome extension.
de-activating and re-activating breakpoints in the devtools solved my issue
The breakpoints icon is in Developer Tools, on the Sources tab, the icon left of the pause button.
I also use OneTab, am on OSX 10.10.5, Google Chrome Version 46.0.2490.71 (64-bit) - other extensions I have installed are LastPass, Xdebug helper, JetBrains, Postman, DevTools Theme: Zero Dark Matrix, Google Docs (and similar)
The breakpoints solution was suggested here https://stackoverflow.com/a/25623760/1875965
You started the validation at i + 1, it should be i.
Change:
var message = "Invalid Argument for " + (i + 1) + ".";
Into:
var message = "Invalid Argument for " + (i) + ".";
I'm trying to remove the yellow infobar. Tried this, adding that parametet to shortcut with no luck:
C:\Users[USERNAME]\AppData\Local\Google\Chrome\Application\chrome.exe –disable-web-security
What is the correct way to hide this yellow infobar ? Thanks
Add the --disable-infobars flag to your command to prevent the yellow infobar from appearing.
That infobar exists for a reason though: It is to warn that a dangerous feature is being used. I recommend against hiding the infobar, because sooner or later you will accidentally visit your bank's website and another malicious website in the same unprotected browsing session.
While automation testing if you want to disable this yellow bar you can add this code:
var chromeOption = new ChromeOptions();
chromeOption.AddArguments("disable-infobars");
driver = new ChromeDriver(chromeOption);
You can use --app=desired_address_without_brackets. Works in Chrome 80.
Semi-official Chrome(ium?) doc for command line options
it will launch chrome in App mode and hide such infobars (alongside the adress bar and maybe tabs). Not always applicable, but --disable-infobars removed in Chrome 76 anyway.
the one hes talking about is the yellow infobar that tells you they wont update chrome. Its the only info bar that pops up that ive ever come across an is a nusance.select the target box put
C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-infobars
Since its inception few years back, Chrome has become a de-facto IDE for web development. I've been using it's Canary(Version 28.0.1464.0) channel for quite a bit and been happy as a clam.
Only issue that keeps bothering me is the lack of ability to have the DevTools console pane, auto scroll to the last message added. I understand that many folks would prefer to have the current behavior. However I was wondering: Does anyone knows how (if even possible with the current release) to flip the switch and have the console auto-scroll?
Thanks.
Clearing the console and scrolling the bar down to the bottom didn't work for me.
The problem was that I had zoomed out DevTools.
Solution:
Focus the DevTools, e.g. by clicking on the console's > prompt
Hit Ctrl-0 (zero) on Windows, or Cmd-0 (zero) on OS X, to restore the default font-size
Hopefully then auto-scroll to bottom will start working again!
Thanks to this guy for pointing it out:
http://code.google.com/p/chromium/issues/detail?id=161646#c5
One Reason why it's happening:
Logging of HTML elements into the console makes the console view lose the last console message.
How to solve it:
Instead of doing something like this:
console.log("Some logging message:", html_element)
try this (wrapped the messages with brackets)
console.log(["Some logging message:", html_element])
It drove me crazy too and I found the solution here:
Google Chrome follow developer console logging
With the console open, drag the scroll bar down to the bottom of the
window and release it. It should tail the output for you.
It does not matter if you have the console docked or not.
Working for me on a osx 10.8.5 and chrome 31
In Chrome version 29.0.1547.76 m, it auto-scrolls when you undock the console. It stops auto-scrolling if you click on the console, then you'll have to clear the console before auto-scroll will be ready to start again.
The "Undock into separate window." button is the bottom-left most button of the console.
For me I've noticed that the autoscroll stopped when the console showed a warning so I've filtered out the warnings and all is good:
For me the only solution that worked was:
click F1 (settings)
At the bottom restore defaults and reload.
None of the above worked.
I found this solution in Chrome 49+
Go Dev-tools/ Settings /
"Console tab"
x Preserve log upon navigation.
Done!