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
F3327537: D25706.1743441266.diff
Sun, Mar 30, 17:14
F3319040: D25706.1743296980.diff
Sat, Mar 29, 01:09
F3317738: D25706.1743266777.diff
Fri, Mar 28, 16:46
F3298769: D25706.1743008829.diff
Tue, Mar 25, 17:07
F3298531: D25706.1743004173.diff
Tue, Mar 25, 15:49
F3292988: D25706.1742904056.diff
Mon, Mar 24, 12:00
F3290942: D25706.1742875662.diff
Mon, Mar 24, 04:07
F3290482: D25706.1742866782.diff
Mon, Mar 24, 01:39

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.