Hmm, I am not able to save the file to my personal dropbox account either,
on 60.0.3112.90 (Official Build) (64-bit) Linux.
On Mac, I could use the "save" button on stable 59.0.3071.115 or 60.0.3112.90,
but could not on canary 62.0.3178.0 (same result as yours).
So from my experiments M60 could still be affected (at least on Linux).

I don't see any suspicious error message on JavaScript console, so I'm not sure
what is going on, also not sure any change caused the saver code to stop
working.

I'd suggest you'd contact DropBox first so they can identify the issue, and
if there is something that we can fix, we can work on it.

Hrm. I pulled down 60.0.3112.90 on Ubuntu LTS and was able to save without issue, so it looks to me like it's something consistent with builds of Chromium at least. I could certainly contact Dropbox about this, but I suspect, given the evidence that they'd just direct me back to here. :-)

The NextAction date has arrived: 2017-08-21

This is still broken in Chrome Beta 61.0.3163.49 on all platforms. It breaks Dropbox integration for thousands of web sites.

Works in Chrome 60 (stable release channel).

You can easily see the repro by clicking on the Save to Dropbox button in their documentation site: https://www.dropbox.com/developers/saver.

[Bulk Edit]
URGENT - PTAL.
M61 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP. 

Know that this issue shouldn't block the release?  Remove the ReleaseBlock-Stable label or move to M62. Thank you!

Note: We will only have 2 beta releases before Stable promotion. Plan is to cut M61 Stable RC on 08/31/17.

Can you paste the output of chrome://version and especially the Variations part for the release you are able to repro with? Also, does it repro if Chrome is started with --disable-features=browser-side-navigation?

It does still repro with --disable-features=browser-side-navigation.

I don't think it is specific to any particular flavor of Chrome (it also repros on my Windows v61 VM for instance) but here's the output of chrome://version:

Google Chrome	61.0.3163.49 (Official Build) beta (64-bit)
Revision	97efb89dab9d3a6340b8e86378baafedff752f3b-refs/branch-heads/3163@{#578}
OS	Mac OS X
JavaScript	V8 6.1.534.22
Flash	27.0.0.96 /Users/jensen/Library/Application Support/Google/Chrome/PepperFlash/27.0.0.96/PepperFlashPlayer.plugin
User Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.49 Safari/537.36
Command Line	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end
Executable Path	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path	/Users/jensen/Library/Application Support/Google/Chrome/Default
Variations	c04e5123-cf4f6ead
6c18ba9d-10f9cf26
c68ab9a3-6edc92c7
38eb801c-3f4a17df
7c1bc906-f55a7974
47e5d3db-3d47f4f4
776de70c-e0278d3d
79616653-3f4a17df
a605b19e-ca7d8d80
5ca89f9-f23d1dea
9e201a2b-d151e2f5
d0165945-3f4a17df
b21cf1cf-ca7d8d80
68812885-3f4a17df
94702c12-8e8e4a2b
f347910c-f23d1dea
b791c1b8-f23d1dea
9773d3bd-f23d1dea
99144bc3-dc4a3f77
9e5c75f1-abc77297
f79cb77b-3d47f4f4
23a898eb-3f2db5fb
4ea303a6-ecbb250e
d92562a9-97fcc22f
de03e059-e65e20f2
ad6d27cc-7075cd8
b2f0086-93053e47
4bc337ce-f23d1dea
1354da85-f34af386
494d8760-1410f10
3ac60855-486e2a9c
f296190c-116bbed1
4442aae2-a5822863
ed1d377-e1cc0f14
75f0f0a0-4ad60575
e2b18481-e1cc0f14
e7e71889-e1cc0f14
644b8345-f23d1dea
94e68624-f23d1dea
828a5926-8f2c913

Can someone bisect this? It will be useful to narrow down what causes this regression and to ensure it is/is not related to PlzNavigate.

I am able to reproduce the issue working on bisect now.

Please find the bisect result below :

You are probably looking for a change made after 478589 (known good), but no lat
er than 478590 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/48e5a7f1adf55ec695f3c24bdf648db251b933d3..7bcb9ee52f2600bafddabaed884ccfea52916753

oop's forgot to update that this is across the platforms, Since blink I am tagging android as well.

Looks like Dropbox is trying to access `u.getAttribute("nonce")` in https://cfl.dropboxstatic.com/static/compiled/js/packaged/pkg-core.min-vfl7GBVS6.js, which won't work in the brave new world of hidden nonce values.

Dev (CCd), how would you feel about replacing that with something like `u.nonce || u.getAttribute('nonce')`? (I feel like we talked about this before... :) ).

huh .. I thought we fixed this. taking a look. 

I think I know whats happening. Found one place where we overlooked this change. Sorry .. working on this. should be fixed tomorrow. thanks for escalating to me.

Per comment #18, no fix is needed from Chrome side, correct?

I am removing the release block stable since this is external dependency.

This appears fixed in the version of Dropbox Saver pushed today.

yup. Sorry again and thanks for filing the bug and escalating here.

Thanks, Dev!