Yeah, js.swc exposes APIs that may not work in all browsers. Be careful what you use when you go low-level.
At the same time, if someone isn't interested in IE9 at all, it wouldn't be a very good experience for them if we completely blocked those low-level APIs that are fully supported on more modern browsers. - Josh On Nov 28, 2016 8:36 AM, "Alex Harui" <aha...@adobe.com> wrote: > > > On 11/28/16, 1:14 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" > <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> > wrote: > > >I just tried to compile a line with classList and seems we have the API in > >flexjs. Don't try it...already, so If we have the API and compiles, it > >should work, so we are supporting it, right? > > I think you are referring to the fact that classList is in the browser > externs. I don't think there is a classList property in the FlexJS swcs. > You can use whatever you find in the browser externs, they just may not > work at runtime in some browsers. > > Maybe I should clarify that the IE9 baseline is only for the Basic > component set. Anybody is welcome to create other component sets that > have different requirements. That's why there is an HTML5.swc. IMO, for > MDL, maybe nobody will care if it doesn't work right away on IE9. > > -Alex > >
