diff options
| author | mkwst <mkwst@chromium.org> | 2016-01-25 06:30:42 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-01-25 14:31:53 +0000 |
| commit | f5cdfde9135883c6cd83c81436ebe4888c432b8b (patch) | |
| tree | 1c154bdc96b1d0575fc336123c98f43d960067f5 /chrome/browser/safe_browsing/incident_reporting | |
| parent | 7d0d2b2fe3902bdcd3e7926c6a67f4af6506c9ef (diff) | |
| download | chromium_src-f5cdfde9135883c6cd83c81436ebe4888c432b8b.zip chromium_src-f5cdfde9135883c6cd83c81436ebe4888c432b8b.tar.gz chromium_src-f5cdfde9135883c6cd83c81436ebe4888c432b8b.tar.bz2 | |
Add a fragment change exception to history API's unique origin restrictions.
Things like jQuery Mobile and Apple's Keynote use hash changes via
'replaceState' for routing. Treating 'file:' URLs as unique breaks them.
We can fairly safely carve out an exception for changes that only effect
the URL's fragment identifier ('#...'), and doing so will prevent breakage.
BUG=528681
R=jochen@chromium.org
Review URL: https://codereview.chromium.org/1632513002
Cr-Commit-Position: refs/heads/master@{#371238}
Diffstat (limited to 'chrome/browser/safe_browsing/incident_reporting')
0 files changed, 0 insertions, 0 deletions