Thoughts: Windows 8 should have eliminated the legacy right click menu.


Recommended Posts

Every regular forum visitor here knows how passionate I am about Windows 8, but there are a few things things that I would have done differently. I have been using Windows 8 on a regular basis across my devices, which includes both touch and non-touch hardware. I have come to the conclusion that Microsoft did not do enough to eliminate old, troubled paradigms from Windows to make them more "Modern", and one of those is the classic right-click menu. Now, there's a few reasons for this. It would make the right click menu more keyboard and touch friendly, while doing more to merge the old with the new.

Since Microsoft has the desktop enabled by default in all forms of Windows 8 and RT, there should have been more done to eliminate troubled code. The right click menu is just not satisfactory enough anymore, and since Windows 8 introduces the new "slide-out" menu on the right side of monitors, they could have easily added right-click menu functionality into the slide out menu. The Settings Charm would be the logical option to go with here. Now, obviously, I think the Charm would need to be re-named... "Functions", "Options", or something more consumer friendly along those lines.

Now, I know there are those that don't like Metro at all. Please, if you're just going to slam Metro and Windows 8, then obviously, now is the time to keep your thoughts to yourself. This is a discussion about a design option I feel should be there but isn't, and not one about whether or not Metro "sucks". Thank you.

Here's what it could look like on the desktop. The crossed off options are either better placed elsewhere, or are considered by me to be obsolete.

post-420821-0-59735300-1347042658_thumb.

The Explorer right click option is even more obsolete in Windows 8, due to much of the functionality appearing on the Ribbon at the top of the window. In fact, upon further inspection, ALL of the right click's functionality is duplicated in the Ribbon. So, it would be nice if the right click menu was gone, and I could access the entire Charms Bar (Win+C on the keyboard) just by right clicking here.

In essence, this guy's usefulness has come to an end, and should have been eliminated before Windows 8 RTM'd, but for some reason it was overlooked, and now users forced into the desktop on less than ideal devices have to put up with this, which is truly and awful experience. Microsoft, I hope you see this and take this into consideration for future releases.

Thanks.

Personally, I'm not a fan of the idea.. well I do like the concept, but not nuking the context menu entirely. Some of us have either customized and/or added on various shell extensions that really make that context menu rather large, never mind compatibility with previous stuff would be problematic or non-existant. Just between SVN and Git alone there's an awful lot of entries that would be problematic or cumbersome, and I've got a fair number more besides that from various utilities, scripts and whatnot.

Definitely make it in addition to what's already there, that would be handy in certain scenarios, but not kill it outright. I've dealt with context menus on a Windows tablet since the XP days, it's certainly not easy to hit accurately with a finger, and this setup would definitely be handy, but on a desktop system the context menu would just be a lot more convenient and efficient. Make it an optional and I'd be sold for sure.

  • Like 2

Thankfully they didn't do this. I like Windows 8, but the day they make a change like this is the day I switch to a different operating system.

On a touch screen, perhaps, but with a traditional keyboard/mouse set-up this would just be an annoyance and make people less productive (significantly more mouse movement).

You seem to completely miss one of the context menu's main advantages... :huh: (namely, the way they reduce the distance to your click target to zero or close enough)

I know this increases travel time, but with the way you can increase cursor speed today, it's a non issue. I can can cross my screens with only a slight bend in my wrist.

I know this increases travel time, but with the way you can increase cursor speed today, it's a non issue. I can can cross my screens with only a slight bend in my wrist.

So can I with a 5200 dpi RAT 5 mouse, the answer is the same.

So in what way is it an improvement then?

Use Windows on a tablet and try to bullseye the context menu items with your finger, it would be a huge improvement. Just needs to be an optional feature, on a desktop setup it would drive me batty having to navigate through a bunch of menus because of all the shell extensions I'm using, assuming they'd work at all. Simple on/off toggle and everybody's happy.

Ugh, no thank you. Usability has already taken enough of a hit as is.

There's no usability being lost here.

Personally, I'm not a fan of the idea.. well I do like the concept, but not nuking the context menu entirely. Some of us have either customized and/or added on various shell extensions that really make that context menu rather large, never mind compatibility with previous stuff would be problematic or non-existant. Just between SVN and Git alone there's an awful lot of entries that would be problematic or cumbersome, and I've got a fair number more besides that from various utilities, scripts and whatnot.

Definitely make it in addition to what's already there, that would be handy in certain scenarios, but not kill it outright. I've dealt with context menus on a Windows tablet since the XP days, it's certainly not easy to hit accurately with a finger, and this setup would definitely be handy, but on a desktop system the context menu would just be a lot more convenient and efficient. Make it an optional and I'd be sold for sure.

It could be something Microsoft could look into opening up for custom entries. It would certainly eliminate the amount of white space currently on the slide out.

I disagree completely! People know me as a big Windows 8 fan, but even I admit that there are certain UI paradigms that work better with mouse and others work better with touch. Context menus work great with mouse, but not touch. At the same time, buttons on the edge of the screen work better with touch. This is why using the Mail app in Windows 8 is so cumbersome. I have to travel my mouse in large distances using my mouse. Mail app using touch is fantastic. I propose that Windows 8 is more adaptable to mouse and touch. Both context menu and app bars should be present so all types of input can be used. Finally, I would suggest that the desktop context menu be the same as the Metro style context menu, just for the sake of consistency.

There's no usability being lost here.

There is indeed, everything about Windows 8 takes more clicks, more mousing around, more scrolling. Usability has taken a HUGE hit with Windows 8. This would be the icing on the cake.

It could be something Microsoft could look into opening up for custom entries. It would certainly eliminate the amount of white space currently on the slide out.

If it's an optional I'm all for it. In fact, if they'd extend the thing to not just simple menus but actual little "widgets" (whatever you'd want to call it), some little extensions that can do basic things besides a menu and it would be even more of a tasty option. Preview videos, view a changelog or edit a Subversion commit, toggle things on or off, etc etc.. lends itself to all sorts of possibilities. Put that RT stuff to good use.

There is indeed, everything about Windows 8 takes more clicks, more mousing around, more scrolling. Usability has taken a HUGE hit with Windows 8. This would be the icing on the cake.

I am just as productive on Win8 as I am on Win7, and the desktop is unchanged. So, define "everything" for me please...

  • Like 2

I am just as productive on Win8 as I am on Win7. Define "everything"....

No thank you, I'm not going to turn another thread into a why we don't like Windows 8, you said so yourself in your first post. My opinion is that this would be a big hit in terms of usability, which is likely the biggest reason I don't like Windows 8, so really, I'm surprised they didn't do this. Chalk it up to another feature that wouldn't be bad on a touch interface, but is terrible for a desktop. I like your creative thoughts, don't get me wrong, but I in no way think it's a good idea for a desktop. If you're offering it for a tablet, then perhaps it's not as bad of an idea.

No thank you, I'm not going to turn another thread into a why we don't like Windows 8, you said so yourself in your first post. My opinion is that this would be a big hit in terms of usability, which is likely the biggest reason I don't like Windows 8, so really, I'm surprised they didn't do this. Chalk it up to another feature that wouldn't be bad on a touch interface, but is terrible for a desktop. I like your creative thoughts, don't get me wrong, but I in no way think it's a good idea for a desktop. If you're offering it for a tablet, then perhaps it's not as bad of an idea.

Windows 8 is a new way to do old things, it's a fresh take on the desktop OS, but at the same time, it's incomplete. The little things like I detailed are why. If anything I certainly hope Microsoft updates their Mouse and Keyboard Center to support Windows 8 commands via my mouse. I'd settle for just invoking Win+I just by right clicking.

I am pretty sure 99% of the people would hate this option. There is a reason MS didn't do this: it would have been disastrous. I am going to say that context menus are not going away any time soon. Even in the next few versions of Windows.

  • Like 3

I am pretty sure 99% of the people would hate this option. There is a reason MS didn't do this: it would have been disastrous. I am going to say that context menus are not going away any time soon. Even in the next few versions of Windows.

It's not going away per se here either, just being moved to fill in the white space in the new slide out menu, while making things more universal. The current right click menu is a mouse driven bit that all users a re forced to deal with no matter what device they are using, which in Windows 8 makes no sense anymore when it can be moved to a better spot. It would still exist, as is, in third party apps, since Windows cannot possibly fill that role.

I know this increases travel time, but with the way you can increase cursor speed today, it's a non issue. I can can cross my screens with only a slight bend in my wrist.

Not so if you're on a laptop with a touchpad. Hence the app bars are a pain to use on a laptop. Depending on your sensitivity and speed settings, crossing the screen takes two finger swipes across the touchpad.

Sorry, still don't buy it. It would still be a terrible UI decision in my mind. People expect to get feed back at point of input, not some distance away. Context menu at the point of click is very natural for the brain and less jarring. I am going to say it now: as long as the mouse exists, context menus will continue to be at the point of click, not some distances away. But that's my opinion, but I know that's how it should be.

The Explorer right click option is even more obsolete in Windows 8, due to much of the functionality appearing on the Ribbon at the top of the window. In fact, upon further inspection, ALL of the right click's functionality is duplicated in the Ribbon. So, it would be nice if the right click menu was gone, and I could access the entire Charms Bar (Win+C on the keyboard) just by right clicking here.

Wouldn't that be an inconsistency, since right-click is used to activate the app bar and not the charms bar in Metro apps? It would be like a Start button that only appears on the desktop.

Not so if you're on a laptop with a touchpad. Hence the app bars are a pain to use on a laptop. Depending on your sensitivity and speed settings, crossing the screen takes two finger swipes across the touchpad.

Laptops are also getting special touch drivers pretty soon.

This topic is now closed to further replies.
  • Posts

    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
    • Microsoft Edge 149.0.4022.52 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.52 changelog: Migration to improved V2 architecture for Workspaces. Workspaces, introduced in Edge in 2022, allows users to create durable sets of tabs that can be saved and shared with others. In order to improve reliability and performance of this feature, the following changes are being made: Migrating data for saved Workspaces from OneDrive/SharePoint to Edge Sync service Removing the collaboration/share functionality of this feature For organizations who have disabled Sync through policy, the existing v1 Workspace data will still be migrated to the new architecture. New v2 Workspaces created after migration won't sync across devices and will remain local to each device. This update occurs on a progressive rollout beginning in Edge Stable v145 and will continue rolling out in Edge v149. For more information, see Getting started with Microsoft Edge Workspaces. Feature Updates Passkey Sync for Enterprise Users. Microsoft Edge is introducing support for passkey synchronization for enterprise users, enabling secure, passwordless authentication across devices. Passkeys created in Edge can now be synced seamlessly, improving sign-in experience while maintaining strong security standards. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout. Enterprise WebView2 runtime downgrade via DowngradeVersion policy. Administrators can temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2) using the new DowngradeVersion policy in msedgewebview2.admx. The Downgrade Version policy allows enterprises to mitigate critical regressions by specifying per-application exe-to-version mappings. The Edge Updater installs the target version side-by-side, and the WebView2 Loader redirects targeted apps accordingly. Downgrades auto-expire with each new WebView2 release: apps pinned to N-1 remain on the same version (now becoming N-2) and will auto-update in the next release, while apps pinned to N-2 will revert to the current Evergreen version. The policy applies only to enterprise-managed devices (domain-joined or MDM-enrolled). For more information, see Microsoft Edge WebView2 Policy Documentation | Microsoft Learn. Collections retirement. Collections has been removed in this update. Users can no longer access or use the feature. To keep saved content, users can export it, or move all pages to Favorites before updating to Microsoft Edge Stable 149. For more information, see Organize your ideas with Collections in Microsoft Edge - Microsoft Support. Modern, unified, and updated Look and Feel. Microsoft Edge has updated the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This changes multiple elements of the UX such as spacing, corners, fonts, default colors, etc. Clarify choices surrounding third-party cookie settings. Language under Settings > Privacy, search, and services > Cookies are clarified to better describe the choices users have in managing third-party cookies. Custom primary password retirement. Users are no longer able to create a new custom primary password in Edge Settings edge://settings/autofill/passwords/settings. Any users who are still using a custom primary password will be automatically migrated to device authentication. Additionally, the PrimaryPasswordSetting policy will no longer support the WithCustomPrimaryPassword option. For more information, see Keep your saved passwords private in Microsoft Edge | Microsoft Support. Unifying Copilot Chat policy controls. The Microsoft365CopilotChatIconEnabled policy is the standard for configuring Copilot Chat. Previously, this behavior was controlled by blocking the Copilot extension, either explicitly or by using the * wildcard via the ExtensionSettings or ExtensionInstallBlockList policies. Extension and sidebar policies no longer affect the appearance or functionality of Copilot Chat. Copilot address bar suggestions were also tied to extension policy settings. Starting in Microsoft Edge version 149, admins can use the CopilotAddressBarSuggestionsEnabled policy to manage this behavior. Intune MAM Protected Downloads. The protected downloads feature for Intune MAM is now available for BYOD (Bring Your Own Device) devices, which aren't managed by a tenant. Policy Updates / New policies CopilotAddressBarSuggestionsEnabled - Enable Copilot address bar suggestions CpuPerformanceTierOverride - Override for the CPU performance tier DataUrlInWebWorkerOpaqueOriginEnabled - Enable opaque origins for data URLs in Web Workers DefaultLocalFontsSetting - Default Local Fonts permission setting ForceForegroundPriorityForUrls - Force foreground priority for specific URLs LocalFontsAllowedForUrls - Allow Local Fonts permission on these sites LocalFontsBlockedForUrls - Block Local Fonts permission on these sites Deprecated policies WalletDonationEnabled - Wallet Donation Enabled (deprecated) EdgeWalletEtreeEnabled - Edge Wallet E-Tree Enabled (deprecated) Additional policy changes ForceForegroundPriorityForUrls - ForceForegroundPriorityForOrigins is renamed to ForceForegroundPriorityForUrls OnSecurityEventEnterpriseConnector - Add macOS platform support ProtectedContentIdentifiersAllowed - Remove macOS platform support Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • User: "But is it good?" Microsoft: "Well, no. But it is less bad."
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      80
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!