User Profile
ikjadoon
Bronze Contributor
Joined May 04, 2019
User Widgets
Recent Discussions
Re: Discussion: Add ability to close tabs via double-click
ikjadoon Wooohoo! I also finally found the toggle (as it came as a pop-up notification the first time), as well, for anyone looking for it. Settings → Appearance → Customize Browser → "Use double-click to close browser tabs" This is on Edge 108.0.1462.46 (Official build) (arm64), running on macOS Monterey 12.6.2. I have absolutely zero of the problems many other users were afraid about: not accidentally closing tabs, not confused, etc. Have no idea what 99% of this thread is worried about: obviously, it is an optional feature.Re: Discussion: Add ability to close tabs via double-click
This feature was recently added (Edge 107.0.1418.35 on macOS confirmed, not sure when it landed) and it is amazing. I love using it and thank you for making it optional. Way easier to use vertical tabs now (which are honestly the best way with macOS's top menu bar). Thank you thank you thank you!Re: 100% CPU usage since Edge 105 on Mac M1 ?
Microsoft is now claiming it is "fixed". I'll test soon on my M1 MBA; quite ridiculous to see such bugs in the stable build. Shouldn't these have been caught in Canary & Beta first? https://www.reddit.com/r/MicrosoftEdge/comments/xmunty/comment/iq5h9ur/?utm_source=reddit&utm_medium=web2x&context=3Re: 100% CPU usage since Edge 105 on Mac M1 ?
Where is the Edge team? This bug has been here for over a week. Does the Edge team only reply after they've shipped the fix? Seems like a waste of a community. This bug is an embarrassment, draining batteries exceptionally quickly. One of the worst software bugs I've ever encountered on macOS. I'm glad to see many others have an identical experience. I thought my laptop was going bad: nope, just Microsoft's bug here. I thought we were on the stable build: shouldn't high-impact bugs like these trigger an "undo commit" situation?Re: Top Feedback Summary for December
Planned | Add option to always open favorites in new tab | 30 weeks Would love to see this for History, too. 😞 This was removed from edge://flags a few months back and it's been a terrible regression for us. We should have an option to open History, Favorites, Downloads, etc. in a new tab.Re: Improvements to history in Microsoft Edge
kamikatze13 Agreed. What a terrible regression. Why not give us the option? It's such a basic feature and decades of muscle memory. For the shortcut key, which is predominantly used by "power users" that I might assume want to see the full page. Until then, I've installed https://chrome.google.com/webstore/detail/autocontrol-keyboard-shor/lkaihdpfpifdlgoapbfocpmekbokmcfd that, using "native extension" APIs, can properly control the shortcut combo. It needs a 300 KB "helper" app, but that allows it to 100% override Edge's confusing behavior. Here's how I've set it up. The "Peek Tabs" autofocuses the newly-created tab. Still, what a ridiculous workaround. Is there any explanation forthcoming from Microsoft? What is wrong with a simple toggle? You've add time to add: ...visual search ...QR codes ...two different PDF viewers And not a single toggle for CTRL+H history full-page. 😞Re: Add a search engine permission: ask when a site wants to add a search engine (e.g., block them all)
Thank you for the update, Alexandra. That's a great explanation; thank you for clarifying it. Yes: unfortunately, sometimes I am looking for information referring to the site itself rather than the institution, say "Github.com bugs". It's not frequently, but it's happened enough where I've twice needed to remove all the extraneous search engines, but of course, they keep repopulating once I ever use the search engine on that site. I'll add this to the Feedback portal!Add a search engine permission: ask when a site wants to add a search engine (e.g., block them all)
Hello! A quick feature request. Today, any site you've visited can add itself as a search engine in your URL bar. Thus, any time you start typing a domain in the URL bar, Edge will automatically try to match your query to the known search engines. I browsed "DeliciousGrilledCheeseRecipies.com" once in my life: why should it get to install a search engine into my browser? Edge should let us block sites from automatically installing themselves as a search engine / provider. This "feature" by website owners is rather anti-user: don't interfere with the browser's search unless a user gives you permission. See for yourself: edge://settings/searchEngines It may be littered with hundreds of sites you once visited years ago. How does this affect a user? If you type any domain name that has installed a search engine, any time you type that domain name + space + any term, Edge now searches within that site instead of Google / Bing. For example, Search engine force installed (today😞 type wirecutter.com union news -> this starts a search on wirecutter.com for "union news" Search engine not installed (feature request😞 wirecutter.com union news -> this starts a search on Google / Bing for "wirecutter.com union news" I didn't want to search on wirecutter.com the website itself, but on Google for content about that website. We could remove the .com, but sometimes you actually want to include the TLD to be specific to the site (e.g., websites with also-an-English-word names like "chase.com" or "google.com"). I want to search about that site, not on that site. understand why it's a feature, so I agree allowing the default to be allow websites to add themselves as search engines, but by creating this new permission, it will allow those of us who'd like to block these uncontrollable search engines and only "install" search engines when we want to.Re: Improvements to history in Microsoft Edge
William Devereux Now that Microsoft has removed the #edge-history-accelerator-override flag in edge://flags, will Microsoft be offering users any way to directly access the complete edge://history page with CTRL+H alone or should we believe that you "no longer believe" in that method as "important enough" for all users? This toggle should've moved to Settings a long time ago. Why are we stuck in edge://flags anyways? As of Version 97.0.1072.55 (Official build) (64-bit), anyways.CTRL + F bug: 1/1 found, but no highlights. Hidden behind ellipsis?
Hello! I've had this peculiar problem on many sites recently. I hit CTRL+F to find a term, it claims it's found and can scroll to the exact area, but there is no visual highlight. Steps to reproduce: https://www.youtube.com/c/MunroLive/videos Open CTRL+F and search for "quantum". Edge will automatically scroll down, but no highlights. Screenshot: Edge has found the term in the HTML (??), but the text—and thus Edge's highlight—is hidden. You may see this as a bug report or a feature request: can Edge ensure it shows some visual highlight even when the text is obscured? To me, the simplest solution is to add a wider highlight with more words on the left / right, perhaps with a lighter / faded highlight. Something like this, if I CTRL+F for "Founder": Interview: Jagdeep Singh, Founder & CEO of QuantumScape The keyword is highlighted the strongest, but the surrounding words also pick up a bit of highlight to ensure even if it's a bit cut-off, we're not losing the text. This would also help with accessibility, as sometimes picking out short strings with a tiny amount of yellow highlighting is difficult. The problem with this solution: what if the word is so hidden that +/- 3 words on either side isn't enough?Re: Is searching history on edge://history slow for anyone else?
ikjadoon After another 30 minutes of troubleshooting, no luck: Reinstalled Edge using https://www.microsoft.com/en-us/edge/business/download. No changes. Cleared Edge's cache. No changes. Ran SFC /scannow. No "integrity violations" and no changes. Tried Edge Dev. Moderately improved, but completely different results (from weeks ago). Disabled activity history in Windows 10. No changes. What an unusual problem. I checked how many items I had and 30k sounds relatively normal: Once the search term is entered, the CPU usage does jump from 0.5% to 19%. But this is a relatively fast CPU (i5-8600K) and it's benchmarking just as fast as it should be (~1200 1T in Geekbench 5). Why it's isolated to a single system does not make sense: aren't these all synced? Unfortunately, Edge Chromium does not have a "repair" install, so back to twiddling my thumbs. Maybe I should install ProcMon again.Re: Improvements to history in Microsoft Edge
Unfortunately agreed that this feature feels a little too buggy to have been pushed to stable. It looks like we'll need to wait a few versions for fixes. It must have been fine for Dev / Canary users? Still having graphical delays / jank as it opens. Still needing a few clicks for search (which will be launching in 3 weeks on 90, but IMHO, it'd have been nice to incorporate that search into its launch as there is no provided fallback). I feel for the JAWS Screen Reader users, as well.Re: Is searching history on edge://history slow for anyone else?
HotCakeX Cheers for the reply. 🙏 It does seem to be a peculiar bug. I'll keep a running log of what's been tested, in case someone else stumbles on this issue and/or there's something to be troubleshooted on my end: Edge updated to 89.0.774.54. No difference. Disabled all extensions. No difference. Unchecked and rechecked History sync. No difference. Some time after step three, the bug disappeared on the laptop at least for a few hours. Rebooted. No difference. Edge Dev is quite weird: with the the same search term, Dev has many more results than Stable, but also does not suffer from the bug. This makes me believe, in fact, Edge Stable is so slow, it's missing many older results (as I stop waiting after 20 seconds). I'll investigate why Edge Dev is working, but Edge Stable is not.Is searching history on edge://history slow for anyone else?
This is on stable using the edge://history dedicated history page (though it replicates on the pop-up menu, but I've avoided that entirely). I've already submitted feedback with video evidence, but I want to make sure it's not just my system here. I can reproduce it on two systems, same Edge & Windows 10 builds. Edge 89.0.774.50 (Official build) (64-bit) Windows 10 Professional x64 20H2 (19042.867) System 1: i5-8600K / 32GB DDR4 / Samsung 970 EVO Plus 500 GB / 400 Mb download / 20 Mb upload / 100% Ethernet System 2: i7-1065G7 / 16GB LPDDR4X / Samsung PM981a 500 GB / same internet / Wi-Fi The main problem is an extremely slow search, as if I'm searching for files on an old hard drive. 1. Open edge://history 2. Type in the left-side search. 3. Wait 3-10 seconds for Edge to populate. 4. Erroneously, you may get "no results found" initially, as even Edge doesn't understand how slow its search is. Example video: https://streamable.com/ohf11y Deleting 1st item: ~1000 milliseconds Deleting 2nd item: ~7500 milliseconds Searching for 'cats': ~7500 milliseconds These are just atrocious speeds. Are others seeing this or is this bug not affecting everyone? It genuinely does not compute why it should be this slow.Re: Improvements to history in Microsoft Edge
William Devereux Thank you so much! That's great to hear and I'll be super excited once 90 hits stable in a few weeks. Definitely a positive improvement for those with decades of muscle memory on how History usually works. I do sympathize with users who like the original edge://history tab (which has great features like natural date filtering like "Yesterday" and "Last Week"). If there's an easy way to open that tab, I can see where they're coming from. I also hope the redraw / performance can be improved. It's currently a not-particularly smooth five-step animation (on an i7-1065G7 / 20H2 / 88.0.705.81), with optional steps for users who do not pin the History tab: (optional) Insert the History icon in the toolbar menu. Load an empty white floating box. (optional) Move the empty white floating box to the left with the icon. Load the top chrome with search and the three-button menu. Load the dark scroll bar. Load the history items (biggest delay here). For #5, perhaps this data (at least the recent items) could be cached? Unfortunately, the same delay occurs with edge://history as a tab, but it feels less bloated because it's a tab (which we associate with websites that often load progressively) versus an in-tab browser menu that we expect to populate all items immediately. The most noticeable seems to be #5, but I'm also confused why #3 and #4 didn't load with #2 automatically. Shouldn't they load instantly? Likewise, removing a history item via the floating "X" has another 300ms to 800ms delay (also occurs in edge://history). A labeled diagram (post-load, it's harder to annotate a video):Re: Improvements to history in Microsoft Edge
William Devereux Great feature and I think it'll be a success, except for one disruptive omission: Can the search text box be focused when we press CTRL+H, so we can start typing immediately? This is muscle memory from every browser: CTRL+H -> start typing. I'm a little worried why some have asked this question, but it's not gotten an official response. For me personally, I know exactly what I'm looking for, but the address bar history is cluttered with way too many other results. In all other browsers / Chromium Edge Prior This Update: Press CTRL+H Start typing Click the result Newest Chromium Edge: Press CTRL+H Click the search icon Start typing Click the result If not, could the Edge feedback team push to include a "fallback" to the previous history UI, i.e,. edge://history with CTRL+H, which did focus the search text box?Re: Introducing Sleeping Tabs Experiment: Improving Memory Usage in Microsoft Edge
Eleanor_Huynh I've been using this for a few days and I gotta say, it's absolutely wonderful. Significantly lower CPU usage, it reminds me to close tabs I'm really not using or just to "get" to them, cooler running laptop, and hopefully it encourages websites to stop running timers all the time. I'd love to read a deep-dive on what was added to Chromium's freeze function to create Edge's sleep function: what are the major differences?
