Closed Bug 1451083 (shumway-webext) Opened 7 years ago Closed 4 years ago

[tracking] Support Shumway as a WebExtension

Categories

(WebExtensions :: Compatibility, enhancement)

Product:
WebExtensions
Component:
Compatibility
Version:
57 Branch
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: e7358d9c, Unassigned)

References

(Depends on 4 open bugs, Blocks 1 open bug)

Details

(Keywords: meta, Whiteboard: [awe:shumway-dev@research.mozilla.org])

This bug serves to track the implementation of the necessary APIs to fully port Shumway to a WebExtension. # Upstream tracking issue: https://github.com/mozilla/shumway/issues/2435
Depends on: 1451545
Depends on: 1451983
Depends on: 1356397
Depends on: 1457500
Depends on: 1318532
Noting that the version of the extension from https://mozilla.github.io/shumway/appears to be incompatible with 62.0a1, but it gives the same error as i've had with certain other add-ons, suggesting it may need to be re-certifcated and the code signature s reconfrimed as valid.
No longer depends on: 1451545
Product: Toolkit → WebExtensions
Keywords: meta
Depends on: 1305109

Flash is dead (soon).
https://developer.mozilla.org/en-US/docs/Plugins/Roadmap

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX

But Shumway doesn’t require the Flash Player Plugin, and its goal is to provide a way to play SWF files long after the Flash Player Plugin is gone for archival purposes.

Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Blocks: 1571368

Isn't Shumway dead? The GitHub repository is archived.

Uh, until like one month ago it didn't use to be like that.

Anyway, ExE had been working on it.
https://github.com/EB-Forks/mozilla-shumway/tree/web-extension

It's just that you still have the blockers in the OP for the moment.

Alias: shumway-webext

Shumway is no longer maintained, this bug can be closed.

Status: REOPENED → RESOLVED
Closed: 5 years ago → 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.