Chrome Canary removes Mapbox access token - google-chrome

since a few days I have problems developing a website with a mapbox map using Chrome Canary (Build: 68.0.3409.0) on macOS.
Problem:
Mapbox is sending requests with a query param access_token=XXXX this param gets a special treatment by Chrome Canary resulting in access_token=anonymized. Therefor mapbox is denying my request.
Screenshot from DevTools Networktab Screenshot from Console
Localy I can reproduces the problem easily and I also created a JS fiddle (https://jsfiddle.net/LiquidSky/xr4rq9zw/) demonstrating the problem, however the offical mapbox examples work fine.
I have no adblocker or stuff installed, just the usual webdev tools.
Question:
Now I wonder if this is related to some security feature coming up in chrome or if this might even be a bug, for which I should open a bug ticket?
Thanks for every info :-D
Kind regards Nico
SOLUTION: Disable Ghostery

Did you get anywhere with this? I have the exact same issue in stable chrome.
It only seems to have caused me issues in the past week or 2 though

Related

google docs on firefox: Saving your changes is taking longer than usual. Editing is temporarily disabled

I am attempting to use google docs with firefox, but am constantly getting this message.
It never goes away.
And if I close the tab all of my work is deleted.
This is a brand new Firefox install.
Is this an attempt to force us back to using chrome with google docs?
I have been a chrome user for many years but was recently forced to switch to firefox because chrome has an intolerable bug on macOS catalina.
I need to use google docs but I can't use chrome because of this chrome bug and now I can't use firefox because of this bug with google docs.
Is there a work-around for the problem?
Chrome allows me to work with local copies of google docs without losing work if I lose my network connection, but I cannot find a similar plugin for firefox.
I tried to reproduce the issue on Firefox, however it seems to work fine at my end without any sort of error or warning popup in saving.
But, Google is known to play nasty with competitors to promote Chrome and it can't be ruled out that it might be a cause too. You can try multiple options, and check which one works.
Possible Solutions:
If you want to trick google into thinking you are browsing on Chrome, change this setting in Firefox as mentioned here!
Try using the Firefox Developer Edition: [Official Link])(https://www.mozilla.org/en-US/firefox/developer/ "Firefox Developer Edition")
If the above options don't work, try switching to Microsoft Edge for a Chrome alternative if the bug is particularly associated with Google Chrome, though they both are based on Chromium, it's worth a try.
Searching through the Google forums, I came across an issue with GDrive not loading in Firefox. https://support.google.com/drive/thread/1987396?hl=en&msgid=22679169
The last comment on the page the user mentions disabling CORS
Find a solution ! When the add-in CORS (Access-control-Allow-Origin)
is enabled impossible to load the google drive page but no problem
when it is deactivated.
Have you tried disabling the CORS? http://testingfreak.com/how-to-fix-cross-origin-request-security-cors-error-in-firefox-chrome-and-ie/
This will happen if you try to copy/paste info from a place that is restricted. Make sure editing is turned on for all users. If it’s not “shared” correctly it will glitch.

Google Chrome developer tools works very slow

Sinсe Google Chrome was updated to 50.x version, it become impossible to work with DevTools. This issue reproduced mostly in "Network" tab. Every time when you click on "request" it takes about 30-40 sec. after that chrome can crash. Tried to delete all extensions, clear cache, and reinstall, but didn't help. Does anybody know how to fix this issue?
I'm running Chrome 50.0.2661.87 m
UPD: The problem may be occurs because of long headers. Try to close response and request headers.
I've been having similar issues for debugging in Chrome versions 50+ on Mac OS X 10.11.3. The only solution I've found so far is to keep the dev tools docked to the right and it seems to be as performant as before. Not the optimal solution, but it works in my case.
Finally, a solution has been found which helped me after such a long time and after so many failed attempts to fix it: Solution on Google Chrome Forums
Go to chrome://flags/#force-color-profile
Change it to sRGB
Since Google does not allow direct links to chrome:// you'll have to insert the colon by yourself, or enter the whole link manually into your toolbar.
My situation was similar, after struggling a while with extreme slow developer tools response I found out the problem was caused by a Chrome extension I had installed for knockoutJs.
So for people experiencing these issues, as part of the initial troubleshooting, try disabling chrome extensions.
I'm using the Version 61.0.3163.79 and I have the same issue that this post talks about.
With some searches I found out that the problem was in the user that I was using. What I tried was to enter int google chrome as guest and the devtools became faster again.
So what I did was:
Check out if debugging using the guest user is faster as it should be.
Logout from the account.
Clean all cache associated to google chrome.
Restart the PC (but i think closing the browser is enough)
Login again in your account.
I hope this could help other people with same problem.
[EDIT:]
I found out that after some time (weeks) the google chrome dev tools will get slower again. So I tried the following solution and it worked:
Open the dev tools
Go to the Sources tab.
Cleaned all watched variables, breakpoints, DOM breakpoint and Event Listeners breakpoint.
[SECOND EDIT:]
After some weeks, the issue came again. What I did was installing the google canary Version 64.0.3249.2 canary (64-bit) and my problems vanished.
For who's that doesn't know what is canary, please check this link.
Google is aware of the problem - https://bugs.chromium.org/p/chromium/issues/detail?id=624097
The problem seems to have vanished in v.53 - they are currently trying to figure out what fixed it. If possible, the fix will be merged back to v.52. But at least they are working on it.
In case others arrive here facing the same issue I had, try changing the Dev tools tab you're looking at to Elements.
I had the "Sources" tab open and Chrome was trying to load enormous assets for that tab, which created a multisecond delay between the console.log() events I created and the display of those logged messages.
Make devtools snappy again by deactivating all breakpoints:
Go to the Sources tab, show the debugger (may be hidden) and hit Deactivate breakpoints.
(Chrome v62.0 on Windows 10)
I've had the same time issue on 54.0.2840.99 m version of Google Chrome.
But switching to Chrome Canary worked !
Reduce size of resource being overridden
Only overriding files with less lines of code worked well for me. I landed here because I was overriding a file which had 35,000 + lines of Javascript.
Further, if your resource is a new one - i.e. it is not included in a script tag or link tag, you can override main html document and add the tag : <script src="/my-new-script.js"></script>. Add the file to your domain-root within the Overrides folder on Chrome:
overriding HTML
then overriding CUSTOM SCRIPT:
Good Luck...
I also face same issue.
I tried unchecked toggle screencast. Now it is working fine.
In my case, I had Local Overrides setup (https://developers.google.com/web/updates/2018/01/devtools#overrides) in Downloads folder which had a lot of files in it and that slowed down devtools.
Setting up overrides in its own seprate directory fixed the slowness.
I sped up Chrome again by doing the following:
Open DevTools -> select Elements tab ->
select nested Computed tab -> under Filter, make sure that Show all is unselected.
select nested Event Listeners tab -> make sure that Ancestors and Framework listeners are unselected.
For me, running Chrome Version 81.0.4044.138 (Official Build) (64-bit) on Ubuntu 18, the problem seems to be the mobile view. When I disable mobile view inspecting becomes really fast again. I think it is caused by touch emulation and other mobile stuff.
To have something similar to a mobile view I move the DevTools dock to the side and resize it until I get the width I need. It is not perfect, but it is useful most of the time.
Besides Chrome, Firefox is much faster when inspecting sites overall, though I didn't use FF because I'm used to specific things on Chrome. Moreover, most of the sites I work with do not trigger these issues on Chrome, in fact, it happens with only one site.
PD: the site that triggers the issue on Chrome Dev Tools has lots of CSS variables. Not sure if that is related.
UPDATE 1 WEEK ago
I was able to use Chrome without issues even in the mobile view by disabling the option "Show media queries"
Go to the network tool and change it without any restrictions. Sometimes this happens if you change mobile settings. Google chrome changes this setting to test mobile device on low internet connection and leaves it that way.

chrome canvas inspector 2015

I used this nifty feature that chrome had for quite a while called "canvas inspector". It was an experimental dev feature that had to manually be enabled.
It was quite helpful when working with webgl via something like THREE.js where you can easily create a bunch of undesired draw calls by accident.
Also, it worked on any website, you could simply take a snapshot and see whats going on in the canvas.
It... miraculously disappeared one day, and google does not give any insight.
I've tried some extensions but they dont feel nearly as good, or i couldn't even get them to work. Is there another way to get this back into chrome?
Apparently it was doing some cheeky stuff that they didn't want in the main project so it was removed in this issue: DevTools: make Canvas profiler an extension
We can make it an extension though. This bug is for tracking removal of the canvas profiler from the DevTools. There will be a separate initiative of porting the code being removed into github and publishing it as a Chrome extension.
According to that issue they might move it to an extension in the future but I haven't found any traces of it as of now. They haven't responded to a question in the above issue about where the new issue could be tracked.
Chrome and Firefox have both removed their Canvas inspectors...
Original Answer:
This is not exactly what the question asks for, but Firefox has a canvas inspector integrated:
https://hacks.mozilla.org/2014/03/introducing-the-canvas-debugger-in-firefox-developer-tools/
You can enable it in the settings of the normal inspector
EDIT: (2019)
The Canvas Inspector has been removed as of Firefox 67:
Mozilla deprecated listing
Bug report with reasoning
Alternative:
spector.js - Recommended alternative by Mozilla
Canvas inspection was just removed!
You can download an old version of Chromium here like Chromium_OSX_43.0.2357.81.dmg. (Provided by freesmug)
Happy Canvas Inspection!
This is the best extension inspector I’ve seen so far.
https://spector.babylonjs.com
First go into
chrome://flags
Then enable
Developer Tools experiments
Then after restarting your browser, open the devlopers tools by hitting f12, then in the top right corner is a gear. Click on it, go to experiments, then find "canvas inspection". It's unstable, but usable.

Webpage displayed in Incognito, not in regular Chrome

So i have been running into this problem with a lot of Wordpress sites lately, usually occurring when i am logged in as Admin, so i couldn't post here because no one would be able to view the problem. However, i just found a site that it happens on that doesn't require admin creds.
http://www.otisports.com/
When i visit this site in Chrome (Version 34.0.1847.137 m), it just displays a blank page. No errors, just the (what now seems standard) event.returnValue is deprecated. Please use the standard event.preventDefault() instead. warning. I have seen that warning signify problems on the site, but they are usually minor, not to the extent that the above URL displays. However, if i open an Incognito window and visit the site everything works perfectly and there is no warning. Does the Incognito window deal with webpages in a way that is so entirely different that it would cause something like this to happen?
I have been racking my brain trying to figure this out. Can anyone reproduce this? is it a bug in chrome?
EDIT: I just tried to open a bounty on this question and the EXACT same thing happened. In Regular Chrome, nothing happened when i clicked the start a bounty link and i saw various errors Undefined is not a function however in incognito everything worked perfectly. what gives?!
EDIT: Yes, i have cleared the cache, history, cookies, everything, and i still get the same errors. I cant even post a comment on this question because of errors...
I came across the same issue when trying to open evernote.com. It loaded successfully while using incognito mode in chrome. Let me share how I fixed this even though the original post is way too old. But maybe someone can find it useful.
I'm using chrome (Version 73.0.3683.103 (Official Build) (64-bit)) running on Linux Ubuntu 18.04.2 LTS.
I tried disabling all extensions and clearing browser data/cache but nothing worked. PS: Disabling adblock previously worked for me. Yes, I stumbled over the same issue before and whitelisting evernote in adblock solved the issue. But it didn't now.
The following is what worked for me:
Open developers tools (CTRL + SHIFT + J).
Navigate to Applications tab.
Choose Clear storage from the side menu
Hit Clear site data button.
After reading the comments I dug into chrome and saw there was a bunch of extensions still sitting around that were definitely malware and I thought I had previously deleted. Instead of picking through them one-by-one, I just deleted everything, re-installed Chrome, and now everything works great!
I had the same issue. My application was working in Incognito mode and in Firefox but not in Regular Chrome. I even disabled all the extensions but no luck. I eventually cleared the Cached images and files because on developer console I found out that the regular chrome was still picking up the old file due to caching. So as soon as I cleared it, my app showed up like a rocket :)
Try removing any non required extension .
Specifically AdBlock
I resolved the problem post that.
Since on Incognito , extensions are disabled, hence page run as expected.
I resolved this unforeseen issue using following steps.
CTRL + SHIFT + DEL > Clear Browsing Data.
Cookies and other site data
Cached images and files
This is for Chrome Browser.
Open Console (Ctl+Shift+I) first.
Then under the application tab, you will find some options on the left, find out the application there, you will find it at the top.
There you will find Service Workers.
Under Service Workers, there will be three checkboxes. Select Update on reload checkbox and reload again.
I had the same issue after installing React-Sight Extention.
The Page hanged but not in the incognito mode.
Try deleting any recently added or junk extension.
Delete your cache.
That worked for me
I had a similar issue in chrome, in my case the problem was that I could log in to my university library's website only in incognito mode. After some digging, I figured out that Google Translate extension was set to automatically translate any page. When I turned that off and instead selected never translate that specific page, it started working in the usual mode as well.
This is rather an old issue but still happens. None of the solutions recommended here and there did not solve the issue in my case.
I somehow noticed this is related with a -some kind of- corruption on the user profile.
This is how I solved it:
Close all Chrome browsers.
Open a Google page on Chrome.
Sign-out from Google (rigt click your profile picture on a Google page, not on the Chrome itself), and sign-in.
If this doesn't work:
Close all Chrome browsers.
Right click Chrome icon and select Google Chrome.
Delete your Google profile on the "select your profile" page.
Close Chrome.
Open Chrome, sign-in.
uBlock Origin was the culprit in my case. Once I allowed the site in uBlock Origin, pages loaded correctly in normal Chrome.

Google Analytics not loading in Chrome

When I try log in to Google Analytics in Chrome, the page doesn't load. Very odd. I just get what you see here:
I've never experienced it before recently, and it works on the same computer with Safari, but for about a week now it hasn't worked on Chrome. Any advice would be appreciated.
Likely an ad blocking plugin that had its ad database updated.
I know this question is old but I thought I'd add my answer.
For me it was adblocker on chrome. Click the hand in the red octagon next to your address bar. Go to options and click "show adds on web or domain", add the the domain https://www.google.com/analytics/ and that should fix it.
Clear your cache and disable any plugins that might be interfering.
Try in incognito or in private browsing as it will stop interference from extensions especially adblocking extensions
I tried on Incognito mode and different browsers but it is still not working. I also tried this on Chrome: Settings > Reset > Restore settings to their original defaults. I am still experiencing the same issue reported in this question. When I gave up trying everything on Windows, I tried from an iPhone (not the app, but visiting Google Analytics from a web browser on my iPhone 7 Plus in Chrome, no success. Then I moved to OS X Yosemite Version 10.10.5, and still the same, Google Analytics was not working. After spending several minutes trying, maybe for about an hour or more without success, it suddenly started working everywhere.
My conclusion is that most likely this was a bug in Google Analytics. I should have tested my Internet speed to see if the cause was poor Internet speed, but other pages were loading correctly. So I assume it was simply some kind of bug in Google Analytics.
EDIT: Today I am experiencing the same problem, and this is about 24 hours after the answer above that I posted yesterday. I went to http://www.speedtest.net/ to test my Internet speed, and these are the results:
Ping: 6ms
Download: 2.68 Mbps
Upload: 5.17 Mbps
Then I saw a pop-up telling me that an internal error had happened, and please close and open again the browser. This was definitely a bug in Google Analytics' service.
This is what I was seeing today, with Google Analytics never loading:
My problem was that google analytics wasn't collecting data from some users using browsers like Chrome and Firefox, and also when the users were active on my website, google's Real Time Reporting didn't work.
I found out that the users were using browser plugins like: AdBlock or disconnect.me wich were blocking the data collection.
I hope this helps someone because google brought me here while I was searching the internet for a solution to my problem.
And with some bits from here and some bits from there I managed to figure out what my problem was.
Thanks.
I had the same problem (Chrome, OSX), but I found out it had something to do with my extensions, as Google Analytics would properly load in Incognito Mode. In my case the extension Windscribe - Free VPN and Ad Blocker were preventing Analytics to load. I fixed it by whitelisting the domain.