Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a list of things that we want/need changed in the Web Extension Spec #56

Closed
flyingzumwalt opened this issue Jul 2, 2017 · 8 comments
Assignees

Comments

@flyingzumwalt
Copy link
Contributor

related to #35

Given our experience building these web extensions, provide a list of things we want or need changed in the Web Extension spec in order to support IPFS in web browsers more cleanly. We will pass this list to the team who are working on the spec.

Example: Allow Web Extensions to provide protocol handlers.

@lidel
Copy link
Member

lidel commented Jul 2, 2017

Things identified during development of firefox add-on rewrite to WebExtension:

@flyingzumwalt
Copy link
Contributor Author

need web workers to support webrtc

@dignifiedquire
Copy link
Member

dignifiedquire commented Aug 28, 2017

need fast, optimized webrtc data channels

@daviddias
Copy link
Member

@daviddias
Copy link
Member

daviddias commented Sep 3, 2017

@lgierth @flyingzumwalt what's the follow up to this thread? Shall we schedule a call?

@daviddias daviddias assigned ghost Sep 3, 2017
@ghost
Copy link

ghost commented Sep 3, 2017

We should make this into a comprehensive, prioritized list that we can point browser people too. Ideally with a brief description which features each of the items unlocks. There are things which are absolute dealbreakers (e.g. proper protocol handlers), and things which are important but not essential. The list should convey this importance and priorities.

@ghost
Copy link

ghost commented Sep 3, 2017

We can then also use this list to track the outreach and progress for each of the items.

@lidel
Copy link
Member

lidel commented Jul 4, 2018

FYSA discussion moved to:

@ghost ghost removed the status/ready Ready to be worked label Jan 30, 2019
@ghost ghost unassigned victorb Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants