We should not be sanitizing 'data:' URL errors |
||
Issue descriptionChrome Version: 58.0.3012.0 OS: All What steps will reproduce the problem? (1) Create a worker with a 'data:' URL (2) Throw an exception from the worker (3) DCHECK is triggered because it thinks the error needs to be sanitized What is the expected result? 'Data:' URL worker errors should not need to be sanitized What happens instead? 'Data:' URL worker errors are treated as if they need to be sanitized Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Feb 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5f11cf4c938565ded9c4268af70e7e578169fa3e commit 5f11cf4c938565ded9c4268af70e7e578169fa3e Author: andypaicu <andypaicu@google.com> Date: Tue Feb 14 13:56:03 2017 Don't sanitize errors if the protocol is "data:" Added a special check for 'data:' URLs to not sanitize error messages. BUG= 691518 , 508734 Review-Url: https://codereview.chromium.org/2690933003 Cr-Commit-Position: refs/heads/master@{#450342} [modify] https://crrev.com/5f11cf4c938565ded9c4268af70e7e578169fa3e/third_party/WebKit/LayoutTests/TestExpectations [modify] https://crrev.com/5f11cf4c938565ded9c4268af70e7e578169fa3e/third_party/WebKit/LayoutTests/external/wpt/html/semantics/scripting-1/the-script-element/data-url.html [delete] https://crrev.com/edebc1fbd29714dce0151bfa57a08b49eea5293d/third_party/WebKit/LayoutTests/external/wpt/html/webappapis/scripting/processing-model-2/runtime-error-data-url-expected.txt [modify] https://crrev.com/5f11cf4c938565ded9c4268af70e7e578169fa3e/third_party/WebKit/Source/core/dom/ExecutionContext.cpp
,
Feb 14 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by andypaicu@chromium.org
, Feb 13 2017