17

I have a website that is returning some odd warning messages and errors in both Firefox and Chrome.

Firefox returns these errors:

GET http://fonts.googleapis.com/css?family=Varela+Round 200 OK 7c8e43d.js (line 18)
13:27:41.46 CSI/tbsd_
13:27:41.48 CSI/_tbnd

Chrome returns this error:

XMLHttpRequest cannot load http://fonts.googleapis.com/css?family=Varela+Round. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin is therefore not allowed access.

I'm guessing that this problem is related to Google Fonts API and Access-Control-Allow-Origin How can I fix the errors for this?

Manolo
  • 24,020
  • 20
  • 85
  • 130
  • @bybe - I've added a screeshot. I can't do much more to add details, as I'm not able to know where it's coming from. – Manolo Nov 29 '13 at 11:35
  • 1
    Also your website has other problems other than that of the Google font, event.returnValue is deprecated. Please use the standard event.preventDefault() instead. (outdated JS or Jquery. Another problem in your HTML code on line 71 for example `logo` should be `logo` missing `""` on the width and src must always have a value otherwise your going to have MIME problems. Anyway, checkout Stack Overflow for problems relating to CODE in future instances. – Simon Hayter Nov 29 '13 at 13:51
  • @bybe - Thank you for edit and your help. Now I know it comes from the fonts. – Manolo Nov 29 '13 at 15:06
  • @bybe - How could I migrate this question to stackoverflow? – Manolo Nov 29 '13 at 15:30
  • Its quite irritating that Google is writing to my console.log. How can I stop this? What happens if they decide to print a 500 page novel to my console? Bad practice... – Charles Robertson Feb 25 '18 at 17:01
  • Why would they ever do that? They're just 2 messages, it won't hurt. If you really don't like it, then `console.log=()=>{}` –  Apr 13 '18 at 22:24

2 Answers2

20

The log entries for CSI/tbsd_ and CSI/_tbnd are not errors but time stamps, which are generated by the Google APIs.

Time stamps can be generated in JavaScript using the console.timeStamp() function.

You can also see these time stamp logs on google.com:

enter image description here

Within Firebug they are even displayed as olive lines within the Net panel timeline:

enter image description here

So these log messages are nothing to worry about. They just provide some information for debugging purposes.

Your actual problem related to the error you get in Chrome is caused by a cross-domain request. So the browser is blocking it for security reasons related to the same origin policy. There's a tutorial on "Cross-Origin Resource Sharing" (CORS) at html5rocks.com.

See also related questions on stackoverflow:

Community
  • 1
  • 1
Sebastian Zartner
  • 18,808
  • 10
  • 90
  • 132
  • 1
    I don't want to see this in my console. Can I stop Google from doing this? – Charles Robertson Feb 25 '18 at 17:02
  • As far as I know, there is no way to stop Google from sending those messages, though at least in the Chrome DevTools you should be able to filter those messages out by typing `-CSI/tbsd_ -CSI/_tbnd` into the filter field. – Sebastian Zartner Feb 26 '18 at 07:47
2

I've also spotted this on my site recently, particularly since adding Google DFP (Doubleclick) code to my page.

I found the following description on this site SpanishDict Engineering

csi?tbsd is a console.time call comng from google

That seems to make sense in the context of my web page. I hope it makes similar sense for you?

Tony Carbone
  • 484
  • 4
  • 10