URLBlacklist policy needs documentation update |
||||||
Issue descriptionThe URLBlacklist policy doesn't work for polymer navigations (see https://bugs.chromium.org/p/chromium/issues/detail?id=731104#c13). We should make sure our policy documentation reflects this, including examples of stuff that won't work (like blocking chrome://settings/passwords)
,
Dec 3
,
Dec 10
bheenan@, what do you think of adding the following? This policy does not prevent the page updating dynamically through JavaScript. For instance, blocking a sub-page of chrome://settings does not prevent navigating to that sub-page from the Settings page.
,
Dec 10
Adding to my queue for this week
,
Dec 10
nicolaso@, LGTM on comment #3
,
Dec 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/34d7a515964aac698a74a94d63303738e836be91 commit 34d7a515964aac698a74a94d63303738e836be91 Author: Nicolas Ouellet-payeur <nicolaso@chromium.org> Date: Wed Dec 12 19:44:25 2018 Add a caveat to URLBlacklist's policy description Bug: 896225 Change-Id: I35a7355a3d3b5fb9ad8d5425e2855985ab36e63a Reviewed-on: https://chromium-review.googlesource.com/c/1370824 Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#616002} [modify] https://crrev.com/34d7a515964aac698a74a94d63303738e836be91/components/policy/resources/policy_templates.json
,
Dec 12
,
Dec 17
Hi Nicolas, I have checked the URLBlacklist's policy description in 73.0.3640.0 but it doesn't look updated (see attached screenshot). The CL is landed in 73.0.3639.0, can you please take a look? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by georgesak@chromium.org
, Oct 17