![]() Since writing about this two days ago, Howard Goldberg has extended the list of observed Search default texts: We still haven’t resolved the question of what triggers a change in the text down in the Search box. Maybe this also explains why the bugs with the new Windows Explorer search bar haven’t been acknowledged by the Windows team … could very well be that the Windows team doesn’t even own that code anymore! If I had to guess, I’d say that what happened here was that the desktop search experience was moved from the Windows team to the Bing web team, and they just don’t have the skills to build desktop programs with efficient C++.Īnd, it looks like there is a mechanism to update the JavaScript code from a remote server, without actually upgrading the Search application itself. There is a lot of evidence in the JavaScript source to suggest that it was built by the Bing team. Which brings me around to the question we’ve all been asking for the past few months: What’s wrong with Search in Win10 version 1909? has a theory that sure rings true with me: No wonder it’s so buggy … that’s way too much unnecessary technology to render a drop-down list. JavaScript is used to render the filtered search results. Which sure looks like a JavaScript smoking gun to me. Only the UI is different.Īs he pushed on his system, he triggered a compilation error (screenshot). ![]() The search box on the Task Bar, and in Windows Explorer, both load C:_(version)SearchApp.exe when you click on them. This of course means that some kind of web rendering engine is required … it’s probably Edge.įurther exploration put the pieces together: I did a little digging around I think I figured out why … the entire search box is now a web application built with JavaScript & React. Click on the Search box and it immediately consumes 120+ MB of memory on my machine. What really sticks out for me with some of these newer Search versions, is that they use a ton of memory. It just broke, all by itself.įor a more detailed explanation, specifically for Win10 version 1909, I’ll refer to on AskWoody : You didn’t give Microsoft permission to break Search. Microsoft reached into your Win10 PC overnight and screwed up its search function. The top-level answer is pretty simple: You didn’t do anything wrong.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |