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
F3712220: D25706.1745678925.diff
Fri, Apr 25, 14:48
F3712171: D25706.1745675033.diff
Fri, Apr 25, 13:43
F3702005: D25706.1745613304.diff
Thu, Apr 24, 20:35
F3686349: D25706.1745576762.diff
Thu, Apr 24, 10:26
F3677592: D25706.1745547887.diff
Thu, Apr 24, 02:24
F3576771: D25706.1745069308.diff
Fri, Apr 18, 13:28
F3503092: D25706.1744797803.diff
Tue, Apr 15, 10:03
F3390671: D25706.1744470177.diff
Fri, Apr 11, 15:02

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.