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
{{ message }}
Repository navigation
HTMLPictureElement interface definition is missing #5323
Our support to these draft specification is normally determined by how the current browsers support it. If it is implemented in most of the browsers, we would add it now. If not, we might hold it and open for discussion.
Activity
RyanCavanaugh commentedon Oct 19, 2015
Looks like this is part of the draft specification. Zhengbo Li (@zhengbli) what's our plan for those?
zhengbli commentedon Oct 19, 2015
Our support to these draft specification is normally determined by how the current browsers support it. If it is implemented in most of the browsers, we would add it now. If not, we might hold it and open for discussion.
rayshan commentedon Oct 19, 2015
If I understand correctly based on this FAQ: https://wiki.whatwg.org/wiki/FAQ#What_does_.22Living_Standard.22_mean.3F, the spec is a "living standard", i.e. will never be "complete" or "frozen".
For reference: http://caniuse.com/#feat=picture (currently shows 54%)
zhengbli commentedon Oct 19, 2015
Looks like Firefox and Chrome are already supporting it, plus Edge is also adding support soon. It should be added in then.
mhegazy commentedon Dec 8, 2015
PRs are welcomed. here is some documentation for adding new types to lib.d.ts: https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md#contributing-libdts-fixes