desktop-pwas: Refactor navigator_content_utils validation functions
Manifest-based registration for protocol handlers should, as much as possible, use the same validation logic used by `registerProtocolHandler`. In order to do that we needed to modify NavigatorContentUtils a bit for some of the validation functions not be dependent on objects not known to the manifest parser (e.g.: Document, ExceptionState..). Instead, we extract some error handling logic out and pass arguments in the format ready to be validated. A subsequent CL will include modifications for the manifest parser to consume from the functions exposed here. Bug: 1019239 Change-Id: I38189e305b67a4ccb9820cbb450546e056774c97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227469Reviewed-by:Lorne Mitchell <lomitch@microsoft.com> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Reviewed-by:
Gyuyoung Kim <gyuyoung@igalia.com> Commit-Queue: Fabio Rocha <fabio.rocha@microsoft.com> Cr-Commit-Position: refs/heads/master@{#775254}
Showing
Please register or sign in to comment