Can't wait for Matrix to become the defacto tool to connect teams, instead of dropping IRC for Slack, they will drop IRC for Matrix. It makes me sad to see JQuery moving to Slack when I think they would be better off moving to Matrix instead. I hope they at least considered Matrix.
The Future of JQuery UI and JQuery Mobile
81–90 of 97 posts
Re: The Future of JQuery UI and JQuery Mobile
#82Earlier quoted context omitted.
Array.from(document.querySelectorAll('.myclass')) .forEach(el => el.style.display = 'block')
Though ie11 doesn't have Array.from()
Re: The Future of JQuery UI and JQuery Mobile
#83Earlier quoted context omitted.
jQuery UI was also tightly tied to Filament Group so it was a commercial product looking to capitalize on the jQuery name. That whole think was not so successful and jQuery UI was never that great. 5+ years ago it was bloated and buggy and it has not seen much development since.
Filament Group was a sponsor but the project was not "tightly tied" to the company. I believe that's a bit of FUD right there.
Re: The Future of JQuery UI and JQuery Mobile
#84The slack url in this post overflows the text and zooms the page out on my phone making for an apropos blog reading experience about the future of jQuery mobile. Photo here https://twitter.com/potench/status/943950784592363520
Bahahaha
Re: The Future of JQuery UI and JQuery Mobile
#85Re: The Future of JQuery UI and JQuery Mobile
#86Can't wait for Matrix to become the defacto tool to connect teams, instead of dropping IRC for Slack, they will drop IRC for Matrix. It makes me sad to see JQuery moving to Slack when I think they would be better off moving to Matrix instead. I hope they at least considered Matrix.
Re: The Future of JQuery UI and JQuery Mobile
#87I understand jQuery is old, but do not have fresh information on what's used nowadays.
Re: The Future of JQuery UI and JQuery Mobile
#88Earlier quoted context omitted.
Though ie11 doesn't have Array.from()
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?
Re: The Future of JQuery UI and JQuery Mobile
#89Earlier quoted context omitted.
The page I linked has a compatibility chart that says Edge 16 has it (no idea if that's a planned release, haven't ever used Edge).
You can use Array.prototype.forEach.call(nodelist, fn), or Arrays.from(nodelist).forEach
Array.prototype.forEach.call(document.querySelectorAll('div'), console.log)
seams to workRe: The Future of JQuery UI and JQuery Mobile
#90jQuery is still quite relevant and helpful. Despite the hype with newer libraries, jQuery is used on 73% of _all_ websites. https://w3techs.com/technologies/overview/javascript_library... I often tell myself, ok, I'm going to just use vanilla JS for this one, but compared to jQuery, it's way too verbose. Try doing $('.my-elements').show() in vanilla js. The problem is the jQuery foundation has become too bureaucratic…
That's actually a good example. My gut feeling was simply to write the following. document.getElementsByClassName("my-class")[0].style.display = 'block'; The PlainJS site mentions that it's not quite that simple and suggests writing your own show() and hide() functions if you're avoiding jQuery. https://plainjs.com/javascript/effects/hide-or-show-an-eleme...