What does a specific widget toolkit have to do with native applications in general?
Sure, there are some legacy and niche apps that are native on desktop
People still use office suites, raster and vector graphics editors, CAD, 3D modelers, meshing and texturing tools, media players, P2P clients, text editors, various format readers and writers, etc. that are largely dominated by native.
Even most non-HTTP network clients (like IRC and FTP) are still predominantly used as native apps because of the far superior experience they bring.
1) Office suites --> Largely a legacy app suite... and web use is increasing for both Office and due to Google Apps.
2) Media Players -- Playing local media is done by native apps, but that is becoming an increasing niche scenario. I posit that Netflix, Pandora, and YouTube dominate other media players.
The most important native app that most people use is their web browser. :-)
Not that I think it's particularly true. I think the desktop form factor is going away, but what replaces it is not so much web as it is responsive / adaptive, and web is a subcategory of that, with mobile being another. Having a UI which is only usable through keyboard and mouse sitting behind a desk just doesn't cut it anymore.
I'm not saying that's what they use, it could be WebSQL, IndexedDB, FileAPI - local data storage is built into your browser.
I think the biggest change is that people have mostly stopped paying for desktop apps, outside of professional tools. I have yet to buy a program written in HTML and JavaScript, though I have paid for content and services provided through such apps.
When was the last time someone told you about an app idea and you had any vision of a Win32 (or WPF) app? The web is the defacto app platform for desktop today. Sure, there are some legacy and niche apps that are native on desktop, but mostly everything new is web based on desktop.
Mobile is a different story, but I think its due mostly to the fact that mobile HW is still changing rapidly. New sensors and other capabilities to tap into, where a standards web has to catch up. But I think this gap too will go away as mobile HW matures.