jQuery 3.0 Released

Post by drinchev » Fri, Jun 10, 2016, 11:58 AM UTC

Sir_Cmpwn wrote: post #31

drinchev wrote: post #11

Earlier quoted context omitted.

True. Although whenever I see a jQuery plugin like that I try to replace it with some combination of "components" [1]. There is a lot of progress in that area. There are stuff like : File picker [2], dropdown [3], tip [4] for tooltips and many more. 1 : https://github.com/component 2 : https://github.com/component/file-picker 3 : https://github.com/component/dropdown 4 : http://component.github.io/tip/

The dropdown and tooltips look useful, but FYI it's really simple to make a file picker. Just put a hidden input type="file" on the page, then: document.getElementById("that-element").addEventListener("change", function(e) { // e.target.files }); document.getElementById("that-element").click();

    document.getElementById("that-element").click();

        /** Creates the click on the input */
        const clickEvent = document.createEvent( "MouseEvents" );
        clickEvent.initEvent( "click", true, false );
        document.getElementById("that-element").dispatchEvent( clickEvent );

Post by Sir_Cmpwn » Fri, Jun 10, 2016, 12:06 PM UTC

drinchev wrote: post #41

Sir_Cmpwn wrote: post #31

Earlier quoted context omitted.

The dropdown and tooltips look useful, but FYI it's really simple to make a file picker. Just put a hidden input type="file" on the page, then: document.getElementById("that-element").addEventListener("change", function(e) { // e.target.files }); document.getElementById("that-element").click();

It's not so easy document.getElementById("that-element").click(); doesn't exist. You need to use something like /** Creates the click on the input */ const clickEvent = document.createEvent( "MouseEvents" ); clickEvent.initEvent( "click", true, false ); document.getElementById("that-element").dispatchEvent( clickEvent ); References : 1 : https://developer.mozilla.org/en-US/docs/Web/API/EventTarget... 2 : http://stack…

Post by JustSomeNobody » Fri, Jun 10, 2016, 12:11 PM UTC

weavie wrote: post #26

drinchev wrote: post #11

Earlier quoted context omitted.

True. Although whenever I see a jQuery plugin like that I try to replace it with some combination of "components" [1]. There is a lot of progress in that area. There are stuff like : File picker [2], dropdown [3], tip [4] for tooltips and many more. 1 : https://github.com/component 2 : https://github.com/component/file-picker 3 : https://github.com/component/dropdown 4 : http://component.github.io/tip/

What is this "components"? I can't find anywhere that explains what it is. Is it just a random collection of javascript utilities?

Post by eyko » Fri, Jun 10, 2016, 12:14 PM UTC

nailer wrote: post #32

rcarmo wrote: post #30

Whenever a new version of jQuery (or Zepto) comes along, I wonder what would have happened if web development borrowed a page from other ecosystems and browser runtimes had subsumed the jQuery API, shipping it natively. It's a controversial notion, I'll grant, but what if the DOM APIs had been replaced by "native" jQuery support? Would we have been better off? Worse? Considering the intricacies of standards bodies an…

Well it's 2016 and we still don't have nodeList.forEach() so it can't be much worse.

Post by Jgrubb » Fri, Jun 10, 2016, 12:19 PM UTC

eyko wrote: post #47

nailer wrote: post #32

Earlier quoted context omitted.

Well it's 2016 and we still don't have nodeList.forEach() so it can't be much worse.

Array.from(document.getElementBy...).forEach ?