You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lit-next will end up using some 'newer' APIs that might not already be implemented in the polyfills. We should take an inventory of these and implement them. Some of the ES specific ones will probably be implemented in Babel / Closure, so we might not want to provide our own polyfill for those.
bicknellr
changed the title
[lit-next] Implement changes for lit-next (newly used DOM APIs, etc.)
[lit-next] List and implement changes for lit-next (newly used DOM APIs, etc.)
Sep 17, 2020
bicknellr
changed the title
[lit-next] List and implement changes for lit-next (newly used DOM APIs, etc.)
[lit-next] List changes for lit-next (newly used DOM APIs, etc.)
Sep 17, 2020
lit-next will end up using some 'newer' APIs that might not already be implemented in the polyfills. We should take an inventory of these and implement them. Some of the ES specific ones will probably be implemented in Babel / Closure, so we might not want to provide our own polyfill for those.
Known so far:
Map
(example),Set
WeakMap
(example)Symbol
(example),getOwnPropertySymbols
String#endsWith
(example)Array#fill
(example)Array#from
(example)Object#is
Element#append()
(example, PR #389)Element#remove()
(example, PR #390)Element#classList
(example)Element#getAttributeNames
EventTarget#addEventListener
and#removeEventListener
withoptions
object parameter (example)Text
constructor (example)CustomElementRegistry#upgrade
(already implemented)The text was updated successfully, but these errors were encountered: