Open Bug 1808701 Opened 1 year ago Updated 4 months ago

Mixed content display upgrades after https-first upgraded

Categories

(Core :: DOM: Security, task, P3)

task

Tracking

()

People

(Reporter: t.yavor, Unassigned)

References

Details

(Whiteboard: [domsecurity-active])

Attachments

(1 file)

Mixed content display upgrade should be performed if page was successfully upgraded from https-first.
So we need at least test coverage for the interaction between https-first and mixed conent display upgrade

Assignee: nobody → lyavor
Whiteboard: [domsecurity-active]
Assignee: t.yavor → nobody
Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.