[SalesForce] Chrome 92 breaks button actions (Reset Password, custom VF) in SFDC – Known Issue workarounds

2021-07-26, hundreds of orgs reported being affected by this Known Issue

Summary
As of Chrome version 92, customers may experience issues when working across the Salesforce platform. This impact may appear with buttons that were previously functioning as expected, visualforce pages/components, or other content not performing as expected. In the Chrome developer console logs impacted users will see the following error:

A different origin subframe tried to create a JavaScript dialog. This is no longer allowed and was blocked. See https://www.chromestatus.com/feature/5148698084376576 for more details.

Are there any other workarounds besides those listed?

Best Answer

A common reason for the non-functional buttons is the "Are you sure" javascript dialog that you might see encoded on a VF page commandButton like this:

<apex:commandButton action="{!doSomething}" value="Do Something"
                    onclick="if(!confirm('Are you sure?')){return false};"
/>

Not all of the workarounds suggested in the Known Issue may be applicable/practical/possible to your org:

Using Firefox or Safari
Changing the way Chrome is launched

An additional workaround that I have discovered (besides removing the confirm JS function from custom buttons) is to run the application page in SFDC Classic. This also addresses the Reset Password button issue which appears to use the JS confirm dialog mechanism

Note: The Classic workaround does not "work" in Service Console Classic;

Related Solutions

[SalesForce] javascript date on custom button issue..

You're getting the local time zone year, month and day, but UTC time hours and minutes. When it's today here and tomorrow in UTC, your date calculations will become a day behind. Example follows:

Local time: 2013-12-31 22:00 -05:00
UTC time: 2014-01-01 03:00 -00:00

Year = 2013
Month = 12
Day = 31
Time = 03:00

So, you're committing the value of '2013-12-31T03:00Z' instead of '2014-01-01T03:00Z'.

There is no need for any of this code at all. The function sforce.internal.dateTimeToString automatically converts the date/time coordinate to the correct value for you as long as it is a native Date object.

In other words, change your code to:

var SO = new sforce.SObject("Sales_Order__c");
SO.Date__c = new Date();
SO.Id = "{!Sales_Order__c.Id}";
updateSO = sforce.connection.update([SO]);

Do not call sforce.internal.dateTimeToString, as it is already called for you, and as the "internal" suggests, you should not be using that function explicitly.

Edit You need to include the ID value to update a record. This is most likely the problem.

Best Answer

Related Solutions

[SalesForce] javascript date on custom button issue..

Related Topic