Page MenuHomePhorge

Remove workaround for IE8 to avoid mixed content warning
AbandonedPublic

Authored by aklapper on Jun 29 2024, 18:24.
Tags
None
Referenced Files
F2991895: D25706.1740198710.diff
Fri, Feb 21, 04:31
F2990358: D25706.1740177337.diff
Thu, Feb 20, 22:35
F2982816: D25706.1739971920.diff
Tue, Feb 18, 13:32
F2982773: D25706.1739971815.diff
Tue, Feb 18, 13:30
F2981965: D25706.1739943125.diff
Tue, Feb 18, 05:32
F2943406: D25706.1738186936.diff
Tue, Jan 28, 21:42
F2935065: D25706.1737817072.diff
Fri, Jan 24, 14:57
F2925956: D25706.1737637493.diff
Jan 22 2025, 13:04

Details

Reviewers
None
Group Reviewers
O1: Blessed Committers
Summary

Internet Explorer 8 displayed a bogus mixed content security warning when the src attribute was set to javascript:void(0).

See for example https://jira.atlassian.com/browse/CONFSERVER-15590 or https://blog.httpwatch.com/2009/09/17/even-more-problems-with-the-ie-8-mixed-content-warning/

This reverts rP34db006c4b6cc5f7627d582ded3001168f75ca68

Test Plan

None.

Diff Detail

Repository
rP Phorge
Branch
ie8mixedContentJS
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 1382
Build 1382: arc lint + arc unit

Event Timeline

A day later this turns out to be a rather stupid patch. Things should remain as is as javascript:void(0) nowadays may trigger CSP errors.