Microsoft allegedly engaged on extra Mica-style visible alternate options for Home windows 11

through Alexandru Poloboc

News editor

With an overwhelming desire to get to the bottom of things and uncover the truth, Alex spent most of his time working as a news reporter, presenter, and television and radio … Continue reading

  • Are you bored of what the new operating system looks and feels like?
  • Good news Windows 11 fans, Microsoft may add more design options.
  • In addition to Mica, developers are also working on other great design materials.
  • A new tabbed design can be seen in the SDK in Windows 11 Build 22523.

Windows 11 mica

It is already a known fact that Microsoft previously pointed out some future design changes for Windows 11 and the world may have just taken a first look at them without actually realizing it.

There appears to be a new public API for tab design in the SDK in Windows 11 Build 22523. The first information on this topic first appeared on Twitter.

We’re about to take a look at the different style options and it’s up to you to judge and choose your favorite.

Windows 11 could have more style options in the near future

If the images shared in the tweet didn’t really look any different to you, you need some more visual aid to determine which looks best, we’ve got you covered.

There is a way where you can get a deeper look and show how these APIs can affect a real app. To make it easier for you, these screenshots will also be shown throughout the article.

This first one is the acrylic version, which, as we all have to admit, looks pretty darn good. The second choice is the popular mica, followed by the tabbed version.

As you can see, the differences are pretty notable, which means the choices you make will affect the look and feel of your operating system even more.

This is great for users who are always looking for a way to stand out or break the routine, which gives their setup a much more personal feel.

Microsoft may be ready to incorporate mica effects into modern and legacy apps as well. This is apparently seen with a MicaBackdropInApplicationFrameHostTitlebar flag in the latest Windows Insider builds.

And since Redmond-based tech company Microsoft is committed to providing updates to Windows 11 once a year, you can count on all of the design changes in the next year.

Which of the three visual styles featured in this article is your favorite? Let us know what you think in the comments section below.

Thanks very much!

Insufficient detail Difficult to understand Other

Contact an expert

Start a conversation

Closing Edge 95 construct for the Dev channel brings Home windows 11-style visuals and extra

Windows 11 style visuals in Edge Canary

Microsoft today released the final Edge 95 build for the Dev Channel which is making version 95.0.1020.0 available to users. The reason this is the final build for version 95 for the dev channel is because Edge is now following a shortened release schedule, with major version releases now happening every four weeks. This is the build that is now expected to transition to beta channel users as the company prepares to move to the next major release.

As for today’s build, there are a couple of major improvements. First of all, Edge now Windows 11-style design by default, with rounded corners and other updated design elements. In Windows 11, the browser also supports translucent items in the title bar and context menus. So far, these functions have been hidden under an experimental flag. It must be noted, however, that the new design is still in the works, so there may be rough edges and inconsistencies.

The second big improvement is in support for View recovery of PDFs on Edge. With this feature, users can pick up PDFs where they left them, which means that Edge now remembers the page number, zoom status and layout of the document, easily reads long PDF files and presents the reader in the browser as a useful alternative to others Apps. For those who need it, there is an option to disable the feature. The feature is shipped to all Edge 95 users.

Other enhancements made with today’s build include the ability to use a pen to annotate screenshots taken using the built-in web capture tool, support for opening local files in the iOS version of the browser, and adding some new administrative policies.

Here is the full list of new features:

  • Functions activated by default:
  • Administrative guidelines (note that documentation and administrative templates may not have been updated yet):
    • A policy has been added to control whether intranet file links are enabled, which controls whether File: URLs on intranet pages open File Explorer.
    • Support for Chromium Policy Enabled to control whether Cross Origin Web Assembly Module Sharing is enabled.
    • Chromium Policy Support Enabled to control whether the display capture permission policy is enabled.
  • Improved support for opening local files in the browser on iOS.

As usual, there are a number of bug fixes that make it into the browser. Here are the changes that will improve the reliability of the browser:

  • A crash when using the password generator has been fixed.
  • A crash when using the web widget has been fixed.
  • Fixed a crash when navigating an IE mode tab.
  • Fixed a crash when using tab groups.
  • A crash when interacting with info bars has been fixed.
  • Fixed a crash when closing an autofill popup.
  • Cell phone, mobile phone:
    • Fixed a crash on startup.
    • Fixed a crash when changing the device orientation.
    • A crash when logging into the browser has been fixed.
    • A crash on older iOS versions has been fixed.
  • Fixed an issue on Mac where checking for updates in Settings would sometimes crash Settings.
  • Fixed an issue where certain applications installed on the device would cause all tabs to crash as soon as they were opened.
  • A hang when opening Internet Explorer has been fixed.
  • Fixed getting stuck when closing the browser.

And here are the fixes aimed at addressing the changed behavior:

  • Fixed an issue with certain Linux flavors where the browser would not open.
  • Fixed another issue where users would be logged out of the browser after refreshing the browser.
  • Fixed a problem where the video volume was sometimes set to max.
  • Fixed an issue where favorites could sometimes not be clicked.
  • Fixed an issue where importing certain data from other browsers would fail.
  • Fixed an issue where Travel Finder wasn’t showing when it should.
  • Fixed an issue where travel recommendations would not appear in places they should.
  • Fixed an issue where the Define card would sometimes not go away when it should.
  • Fixed an issue where certain banner UI could not interact or be closed.
  • Fixed an issue where the link to test the HTTP version of a webpage on the error page that appears when the HTTPS version of the page is not available does not actually attempt to navigate to the HTTP version of the website.
  • Fixed an issue where PDF titles were garbled as shown in the browser tab.
  • Fixed an issue where pinned websites would sometimes be resolved after refreshing the browser.
  • Fixed an issue with older versions of Windows where browser installation would fail.
  • Fixed an issue where free text annotations in PDFs would not work at the edges of the page.
  • Fixed an issue where download notifications would sometimes not appear in pop-up windows.
  • Fixed an issue where Jump List Actions are missing from PWAs or websites installed as apps on Windows 11.
  • Cell phone, mobile phone:
    • Fixed an issue where InPrivate sometimes couldn’t be used.
    • Fixed an issue where the login screen would get stuck while logging in to the browser.
    • Fixed an issue on Android where menus would sometimes not work when sharing another app with the browser.
    • Fixed an issue where passwords cannot be edited or deleted because nothing works on the Password Settings page.
    • Fixed an issue where rewards would not work.
    • Fixed an issue where the button to go to the Immersive Reader would sometimes not be visible when it should.
  • Developer:
    • Fixed an issue in WebView2 applications where certain resources were left out when the application was published (Issue 730, Edition 1061).
    • Fixed an issue creating WebView2 apps that contain XAML islands (Edition 1716).
  • The administrative policy to control whether Internet Explorer integration tests are allowed has been deprecated.

Finally, there are a number of known issues that users should be aware of that the company will always list on these release notes. Here is the full list:

  • YouTube users may experience playback errors with certain ad blocking extensions. As a workaround, temporarily disabling the extension should allow playback to continue. See this help article for more details.
  • Some users still experience an issue where all tabs and extensions immediately crash with a STATUS_INVALID_IMAGE_HASH error. The most common cause of this error is out of date security or antivirus software from a vendor such as Symantec. In these cases this will be resolved by updating this software.
  • Kaspersky Internet Suite users who have installed the associated extension may sometimes find that websites such as Gmail cannot be loaded. This error is due to the fact that the main Kaspersky software is out of date, so it is resolved by making sure that the latest version is installed.
  • Some users still see favorites being duplicated. This issue should be reduced now that automatic deduplication has been introduced in Insider channels, but we’re still running it in stable. We have also seen duplication occur when the manual deduplicator is run on multiple computers before one of the computers has a chance to fully sync its changes.
  • Some users see “jiggling” behavior when scrolling with trackpad gestures or touchscreens, with scrolling in one dimension also causing the page to scroll subtly back and forth in the other. Note that this only affects certain websites and appears to be worse on certain devices. This is most likely related to our ongoing work to bring scrolling back to Edge Legacy behavior. So, if this behavior is undesirable, you can turn it off temporarily by turning off the edge: // flags / # edge-experimental-scrolling flag.

As always with these builds, they will be released in stages. While not all users will see the update, it should be rolled out to all development channel users sooner rather than later. Additionally, with today’s build released, both the Dev and Canary versions are now on the same version.