View Issue Details

IDProjectCategoryView StatusLast Update
0002778Composrcorepublic2018-02-08 00:20
ReporterChris GrahamAssigned ToChris Graham 
SeverityFeature-request 
Status resolvedResolutionfixed 
Product Version 
Fixed in Version 
Summary0002778: Drop Flash support
DescriptionThis is more of a future note, I don't think we should do it yet.

But at some point we will remove:
1) flash banners
2) the Comcode flash tag
3) the flash media renderer
And generally make sure Flash is erased from any references anywhere.

I think we should only do it when the last major browser has dropped support for the player, or if Adobe stops maintaining the plugin with security fixes.

Up until then Flash still has legacy value, e.g. for people to embed old flash games or ads.
TagsRisk: Deprecates functionality, Type: Standards compliance
Time estimation (hours)1
Sponsorship open

Relationships

related to 0002005 non-assigned Web standards refresh 

Activities

Chris Graham

2017-04-28 14:27

administrator   ~0005035

SoundManager can likely be replaced with pure HTML5.

Chris Graham

2017-07-25 19:34

administrator   ~0005173

https://techcrunch.com/2017/07/25/get-ready-to-say-goodbye-to-flash-in-2020/?ncid=rss

Chris Graham

2017-09-23 17:46

administrator   ~0005197

crossdomain.xml will go when Flash is removed, see default htaccess files for example.

Chris Graham

2018-02-07 21:08

administrator   ~0005462

https://blogs.windows.com/msedgedev/2017/07/25/flash-on-windows-timeline/

Chris Graham

2018-02-07 23:13

administrator   ~0005469

Also we should remove the flash banner from our banners.zip file.

Chris Graham

2018-02-08 00:20

administrator   ~0005470

This is implemented (i.e. Flash is removed).

I have made some exceptions though. I am not removing flash from integrated utility code that uses it as a fallback. This includes: jwplayer, soundmanager, plupload, mediaelement. Flash will be removed from these if these projects themselves remove it and when we upgrade. Having flash as a fallback for old browsers is still a valid use-case.

Issue History

Date Modified Username Field Change
2016-08-13 18:56 Chris Graham New Issue
2016-08-13 18:57 Chris Graham Tag Attached: Risk: Deprecates functionality
2016-08-13 19:44 Chris Graham Description Updated View Revisions
2016-12-08 12:21 Chris Graham Tag Attached: Type: Standards compliance
2017-04-08 14:45 Chris Graham Relationship added related to 0002005
2017-04-28 14:27 Chris Graham Note Added: 0005035
2017-07-25 19:34 Chris Graham Note Added: 0005173
2017-09-23 17:46 Chris Graham Note Added: 0005197
2018-02-07 21:08 Chris Graham Note Added: 0005462
2018-02-07 23:13 Chris Graham Note Added: 0005469
2018-02-08 00:20 Chris Graham Note Added: 0005470
2018-02-08 00:20 Chris Graham Status non-assigned => resolved
2018-02-08 00:20 Chris Graham Resolution open => fixed
2018-02-08 00:20 Chris Graham Assigned To => Chris Graham