Improve the documentation for the ManagedBookmarks policy.

Improve the documentation for the ManagedBookmarks policy.

This change expands the example policy value to demonstrate how bookmark
folders can be configured.

BUG=424181
Committed: https://crrev.com/fa9792b39eab80dfa1c98e3d199fb550c535169f
Cr-Commit-Position: refs/heads/master@{#300457}

[Joao da Silva, 2014-10-17 14:41:47]

joaodasilva@chromium.org changed reviewers:
+ tnagel@chromium.org

[Joao da Silva, 2014-10-17 14:41:48]

PTAL, thanks!

[Thiemo Nagel, 2014-10-20 09:05:39]

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
File components/policy/resources/policy_templates.json (right):

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
components/policy/resources/policy_templates.json:6520: "url": "google.com"
I'd suggest to add scheme and directory parts to make this (and the following)
valid URLs, e.g. "https://google.com/".

[Joao da Silva, 2014-10-20 09:21:39]

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
File components/policy/resources/policy_templates.json (right):

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
components/policy/resources/policy_templates.json:6520: "url": "google.com"
On 2014/10/20 09:05:38, Thiemo Nagel wrote:
> I'd suggest to add scheme and directory parts to make this (and the following)
> valid URLs, e.g. "https://google.com/".

The URLs in this policy work as if they were entered in the omnibox (they go
through the URLFixerUpper to get canonicalized into a valid URL). If you feel
strongly then I'll update this example.

[Thiemo Nagel, 2014-10-20 09:57:07]

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
File components/policy/resources/policy_templates.json (right):

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
components/policy/resources/policy_templates.json:6520: "url": "google.com"
> The URLs in this policy work as if they were entered in the omnibox (they go
> through the URLFixerUpper to get canonicalized into a valid URL). If you feel
> strongly then I'll update this example.

Interesting.  Rather than changing the example I'd then suggest to include this
fact in the documentation.  Just writing "URL" implies RFC 3986 compliance, at
least to my mind.

[Joao da Silva, 2014-10-20 14:22:14]

PTAL

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
File components/policy/resources/policy_templates.json (right):

https://codereview.chromium.org/658393002/diff/1/components/policy/resources/...
components/policy/resources/policy_templates.json:6520: "url": "google.com"
On 2014/10/20 09:57:07, Thiemo Nagel wrote:
> > The URLs in this policy work as if they were entered in the omnibox (they go
> > through the URLFixerUpper to get canonicalized into a valid URL). If you
feel
> > strongly then I'll update this example.
> 
> Interesting.  Rather than changing the example I'd then suggest to include
this
> fact in the documentation.  Just writing "URL" implies RFC 3986 compliance, at
> least to my mind.

Done.

[Thiemo Nagel, 2014-10-20 16:17:45]

LGTM.

[Joao da Silva, 2014-10-21 08:09:14]

The CQ bit was checked by joaodasilva@chromium.org

[commit-bot: I haz the power, 2014-10-21 08:10:08]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/658393002/40001

[commit-bot: I haz the power, 2014-10-21 11:27:04]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2014-10-21 11:27:57]

Patchset 3 (id:??) landed as
https://crrev.com/fa9792b39eab80dfa1c98e3d199fb550c535169f
Cr-Commit-Position: refs/heads/master@{#300457}