ExtensionNavigationThrottle: No platform apps in normal tabs.

ExtensionNavigationThrottle: No platform apps in normal tabs.

This restriction already exists, but there were several ways around
it. The blockage in chrome::Navigate only applied to
browser-initiated navigations; the blockage in the CreateNewWindow
codepath only applied to the initially-requested URL.

This prevents the following scenarios:
 (1) a platform app's background page could open a popup
     with window.open(), and then navigate it back to
     a platform app resource.
 (2) A browser-initiated navigation could be issued to an
     http URL that redirects to a platform app URL.

The only remaining hole I'm aware of is the following scenario:
 (3) a platform app's background page can open an
     about:blank popup with window.open()
That last case will be fixed in the next patch.

BUG=139258, 708870

[ncarter (slow), 2017-04-27 22:05:15]

The CQ bit was checked by nick@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-27 22:29:55]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-28 01:36:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-28 01:36:23]

Dry run: Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[ncarter (slow), 2017-04-28 17:27:30]

The CQ bit was checked by nick@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-04-28 17:28:06]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[ncarter (slow), 2017-04-28 17:33:10]

Description was changed from

==========
ExtensionNavigationThrottle: No platform apps in normal tabs.

BUG=708870
==========

to

==========
ExtensionNavigationThrottle: No platform apps in normal tabs.

This restriction already exists, but there were several ways around
it. The blockage in chrome::Navigate only applied to
browser-initiated navigations; the blockage in the CreateNewWindow
codepath only applied to the initially-requested URL.

This prevents the following scenarios:
 (1) a platform app's background page could open a popup
     with window.open(), and then navigate it back to
     a platform app resource.
 (2) A browser-initiated navigation could be issued to an
     http URL that redirects to a platform app URL.

The only remaining hole I'm aware of is the following scenario:
 (3) a platform app's background page can open an
     about:blank popup with window.open()
That will be addressed in the next patch.

BUG=708870
==========

[ncarter (slow), 2017-04-28 17:34:17]

Description was changed from

==========
ExtensionNavigationThrottle: No platform apps in normal tabs.

This restriction already exists, but there were several ways around
it. The blockage in chrome::Navigate only applied to
browser-initiated navigations; the blockage in the CreateNewWindow
codepath only applied to the initially-requested URL.

This prevents the following scenarios:
 (1) a platform app's background page could open a popup
     with window.open(), and then navigate it back to
     a platform app resource.
 (2) A browser-initiated navigation could be issued to an
     http URL that redirects to a platform app URL.

The only remaining hole I'm aware of is the following scenario:
 (3) a platform app's background page can open an
     about:blank popup with window.open()
That will be addressed in the next patch.

BUG=708870
==========

to

==========
ExtensionNavigationThrottle: No platform apps in normal tabs.

This restriction already exists, but there were several ways around
it. The blockage in chrome::Navigate only applied to
browser-initiated navigations; the blockage in the CreateNewWindow
codepath only applied to the initially-requested URL.

This prevents the following scenarios:
 (1) a platform app's background page could open a popup
     with window.open(), and then navigate it back to
     a platform app resource.
 (2) A browser-initiated navigation could be issued to an
     http URL that redirects to a platform app URL.

The only remaining hole I'm aware of is the following scenario:
 (3) a platform app's background page can open an
     about:blank popup with window.open()
That last case will be fixed in the next patch.

BUG=708870
==========

[ncarter (slow), 2017-04-28 17:40:21]

Description was changed from

==========
ExtensionNavigationThrottle: No platform apps in normal tabs.

This restriction already exists, but there were several ways around
it. The blockage in chrome::Navigate only applied to
browser-initiated navigations; the blockage in the CreateNewWindow
codepath only applied to the initially-requested URL.

This prevents the following scenarios:
 (1) a platform app's background page could open a popup
     with window.open(), and then navigate it back to
     a platform app resource.
 (2) A browser-initiated navigation could be issued to an
     http URL that redirects to a platform app URL.

The only remaining hole I'm aware of is the following scenario:
 (3) a platform app's background page can open an
     about:blank popup with window.open()
That last case will be fixed in the next patch.

BUG=708870
==========

to

==========
ExtensionNavigationThrottle: No platform apps in normal tabs.

This restriction already exists, but there were several ways around
it. The blockage in chrome::Navigate only applied to
browser-initiated navigations; the blockage in the CreateNewWindow
codepath only applied to the initially-requested URL.

This prevents the following scenarios:
 (1) a platform app's background page could open a popup
     with window.open(), and then navigate it back to
     a platform app resource.
 (2) A browser-initiated navigation could be issued to an
     http URL that redirects to a platform app URL.

The only remaining hole I'm aware of is the following scenario:
 (3) a platform app's background page can open an
     about:blank popup with window.open()
That last case will be fixed in the next patch.

BUG=139258, 708870
==========

[commit-bot: I haz the power, 2017-04-28 18:15:31]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-28 18:15:31]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[ncarter (slow), 2017-05-01 21:58:48]

The CQ bit was checked by nick@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-01 21:59:44]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-01 22:45:42]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-01 22:45:43]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[ncarter (slow), 2017-05-17 20:57:32]

The CQ bit was checked by nick@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-17 20:59:12]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-17 23:13:25]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-17 23:13:26]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[ncarter (slow), 2017-05-22 23:05:25]

The CQ bit was checked by nick@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-22 23:06:18]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-22 23:15:36]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-22 23:15:37]

Dry run: Try jobs failed on following builders:
  mac_chromium_compile_dbg_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[ncarter (slow), 2017-05-26 22:04:23]

The CQ bit was checked by nick@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-26 22:04:59]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-26 23:25:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-05-26 23:25:05]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)