Skip to content

Issues: drufball/layered-apis

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.

Sign up for GitHub

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

22 Open 8 Closed
22 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Ja
#42 opened Dec 21, 2020 by Lulu-Lucinka
Remove virtual-scroller from examples
#41 opened Apr 27, 2019 by dfabulich
Should std:xxx be governed by CSP?
#40 opened Mar 14, 2019 by shhnjk
Emoji picker
#39 opened Dec 20, 2018 by nolanlawson
7
Handling of Versions
#38 opened Nov 20, 2018 by jogibear9988
Rich-Text Editing LAPI
#36 opened Oct 9, 2018 by jamiebuilds
3
Should MathML be a layered API?
#35 opened Sep 28, 2018 by valentin-huebner
Fallback user stories fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill
#34 opened Aug 20, 2018 by domenic
6
Explain how LAPIs can use other LAPIs (without monkeypatching interference)
#32 opened Jul 31, 2018 by domenic
Standards venue
#31 opened Jun 26, 2018 by littledan
5
Syntax bikeshedding: package:@std/<name>
#30 opened Jun 20, 2018 by littledan
3
Separating dependency ID declaration from URL resolution via a JS API fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill
#24 opened May 9, 2018 by jrburke
1
2
std:test for testing infra implementations fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill
#17 opened May 4, 2018 by hiroshige-g
std:x|y is not a valid URL fallback syntax An issue with the syntax for falling back from a LAPI to a polyfill
#15 opened May 4, 2018 by hiroshige-g
1
17
Can we/should we make std:x | y work? fallback syntax An issue with the syntax for falling back from a LAPI to a polyfill
#14 opened May 4, 2018 by domenic
1
5
Risks of premature polyfilling
#12 opened Apr 27, 2018 by Jxck
8
Different fallbacks specified in different places fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill
#10 opened Apr 3, 2018 by domenic
1
1
Missing platform ability: Function.prototype.toString() censorship missing platform ability A missing web platform API that is necessary for writing LAPIs
#7 opened Mar 16, 2018 by domenic
Allow multiple fallback URLs fallback semantics An issue with the proposed model for falling back from a LAPI to a polyfill
#5 opened Mar 9, 2018 by domenic
2
Avoiding magic when calling callbacks
#4 opened Feb 13, 2018 by jakearchibald
1
Requiring imports can be suboptimal for custom element layered APIs
#3 opened Feb 3, 2018 by domenic
Custom elements require dashes in the name
#2 opened Feb 3, 2018 by domenic
8
ProTip! Add no:assignee to see everything that’s not assigned.