14

Just today I started having a very odd layout issue on our standard Account layout. The org in on the NA6 server. This is the standard layout. It's always happening when I use chrome. I haven't been able to recreate it in IE, and get it intermittently in Firefox, but definitely it is the worst in Chrome, as it always produces this error. My version is current

enter image description here

The related lists all seem to be in only the right side of a 2 column set up, as seen below

enter image description here

When I check the console I see the error

Refused to set unsafe header 'User Agent'

enter image description here

I look further into it in the console and it appears to be an issue with the SF javascript. In particular the sforce.Transport function. See the errors below

enter image description here

I have opened a ticket with SF and they are investigating, but just curious if anyone else has seen this today, or in the past.

This just started happening this morning.

Improve this question
2
  • It is happening again on the new version #32 of chrome. Do you know if is there any patch?
    – Martin Borthiry
    Commented Jan 22, 2014 at 15:56
  • I am having the same issue with latest version of Safari and Chrome. An ideas?
    – dzh
    Commented Feb 2, 2014 at 0:33

2 Answers 2

Reset to default
9

I'm not sure it's related, but I noticed this on twitter:

.@salesforce users please update your Google Chrome to 31.0.1650.57. This fixes the display issue. Nate Lipke

I think this comes back to the known issue: Unexpected display issue after updating to Google Chrome 31 with embedded Visualforce Pages

Improve this answer
3
  • You are correct, I had to get the latest version. Must be a pretty recent patch. I had to clear the cache and quit out of chrome, then it automatically updated the version. No more errors. Thanks a lot for the help.
    – Chris Duncombe
    Commented Nov 14, 2013 at 21:52
  • There was an email alert today about this about v31 chrome. A second alert reported google had patched the issue.
    – Ralph Callaway
    Commented Nov 15, 2013 at 2:03
  • 1
    This seems to be a different issue - the v31 chrome issue was around embedded visualforce and scontrols in page layouts. I hit the issue described here with the AJAX toolkit (connection.js) a year ago and had to patch connection.js: github.com/capeterson/Grey-Tab/commit/…
    – ca_peterson
    Commented Nov 15, 2013 at 4:04
0

A Way to solve this problem is to make and static resource with the connection.js file and comment the line: //this.connection.setRequestHeader("User-Agent", "SFAJAX 1.0");

Then reference the static resource, this solved my issue and the console is clear of this error.

my two cents.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .