News for hackers. Stuff that matters.

A comment on The Future of JQuery UI and JQuery Mobile. Parent comment

Re:The Future of JQuery UI and JQuery Mobile by tracker1 on Thursday December 21, 2017 @06:23PM (#15983865) 

  Array.from(document.querySelectorAll('.myclass'))
    .forEach(el => el.style.display = 'block')
[ Parent | on HN ]
Re:The Future of JQuery UI and JQuery Mobile by collinmanderson on Thursday December 21, 2017 @07:13PM (#15984117)
Though ie11 doesn't have Array.from()
[ Parent | on HN ]
Re:The Future of JQuery UI and JQuery Mobile by bonesss on Friday December 22, 2017 @04:38AM (#15986310)
Hrmmm... maybe someone should make a library that would smooth over browser differences and provide a consistent element selection syntax? Call it JavascriptSelection, or jSelection?
[ Parent | on HN ]
Re:The Future of JQuery UI and JQuery Mobile by emergie on Friday December 22, 2017 @09:09AM (#15987497)
imho 'JavascriptQuery' or 'jQuery' sounds better, oh wait...
[ Parent | on HN ]
Re:The Future of JQuery UI and JQuery Mobile by tracker1 on Wednesday December 27, 2017 @05:13PM (#16018498)
I tend to polyfill older browsers, Array.from is a pretty small one. Sad thing is at a point where it's probably worth it to have 2-3 builds in place... 1 for legacy browsers, one for modern without modules, and one for modules/import/http2 support.

Just haven't taken the time... at least the main app I work on at work doesn't need to support IE11. Latest Edge,, Firefox, Safari and Chrome ... and Chrome is the primary target.

[ Parent | on HN ]