Mixed content parent frame checking logic might be wrong |
|||||
Issue descriptionWhile working on issue 576270 I found out that when searching for the parent secure context for mixed content checking only the top level frame and the immediate parent are checked, in this order. See the implementation of MixedContentChecker::inWhichFrameIsContentMixed [1]. After discussing this with mkwst@ we think this might be wrong and we should instead check all levels in between. Note that there are layout tests that fail when the top one is not given priority. Note: if issue 576270 lands before this is addressed, the introduced browser side logic should also be updated. [1] https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/loader/MixedContentChecker.cpp?type=cs&q=MixedContentChecker::inWhichFrameIsContentMixed+file:%5C.cpp&sq=package:chromium
,
Jul 1 2016
mkwst@, could you please help in finding the right owner for this issue. Thanks!
,
Jul 11 2016
,
Mar 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 10 2018
,
Mar 13 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by shivanisha@chromium.org
, Jun 29 2016