DescriptionRevert of Implementing mixed content for forms posting to insecure location from secure ones (https://codereview.chromium.org/311033003/)
Reason for revert:
This CL incorrectly integrates with the inspector.
Notice that in Element::didModifyAttribute, InspectorInstrumentation::didModifyDOMAttr will be called with the original value, not the mutated value.
Original issue's description:
> Implementing mixed content for forms posting to insecure location from secure ones.
>
> When a form "action" attribute is pointing to insecure location from a secure one, this is flagged as mixed content. This is even checked if the pages dynamically changes the "action" attribute after the initial loading. The mixed content is non-blocking by default, however, this can be overridden in the preferences, and this will cause a submit to silently fail, other than a console message.
>
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175714
TBR=jww@chromium.org,mkwst@chromium.org,mohammed@chromium.org
NOTREECHECKS=true
NOTRY=true
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175715
Patch Set 1 #
Created: 6 years, 6 months ago
(Patch set is too large to download)
Messages
Total messages: 3 (0 generated)
|