1520197 - [UX] Define UX for in-content Object tags (Flash) when Flash is disabled

Status: RESOLVED WONTFIX

(Firefox :: General, enhancement, P2)

Description

[Jim Mathies [:jimm]]

We'll need UX input on how we want to handle Object tags once flash is disabled by default. Currently we display the click-to-activate UX if the content is large enough, and fall back on the door hanger interface for smaller or hidden objects.

For the latter, I assume we'll just ignore it. But for large Object tags (games, full page flash content) we might want some sort of 'flash is disabled' UX with a link to a SUMO article.

Romain, any suggestions on who should we can pull in from UX on this?

Comment 1

[Jim Mathies [:jimm]]

I think we support flash in Fennec as well, so we might have mobile specific work to do here.

Comment 2

[Chris Peterson [:cpeterson]]

(In reply to Jim Mathies [:jimm] from comment #1)

I think we support flash in Fennec as well, so we might have mobile specific work to do here.

James, does Fennec still support Flash?

Comment 3

[Sören Hentzschel]

Flash support was removed in Firefox 56 for Android:
https://bugzilla.mozilla.org/show_bug.cgi?id=1381916

Comment 4

[James Willcox (:snorp) ([e-mail]) (he/him)]

(In reply to Chris Peterson [:cpeterson] from comment #2)

(In reply to Jim Mathies [:jimm] from comment #1)

I think we support flash in Fennec as well, so we might have mobile specific work to do here.

James, does Fennec still support Flash?

Nope!

Comment 5

[Chris Peterson [:cpeterson]]

WONTFIX because we no longer plan to disable Flash by default prior to removing Flash support entirely. In Firefox 69, however, we will remove the "Always Activate" Flash option and prompt users every time a site wants to activate Flash.

https://developer.mozilla.org/en-US/docs/Plugins/Roadmap