MS Modifies black maximized borders


Recommended Posts

all you babies finally got what you want (sort of!) :p

Just a quick blog post to update you on an issue near and dear to the hearts of some people. Well, at least the 1300 or so people so far who have contacted me about this issue.

Background

In Vista, we are really trying to reduce the amount of high contrast visual noise in the UI to make it more comfortable for daily use. Part of that is make the taskbar darker, and another aspect is making the maximized windows match the taskbar by tinting toward black also. The black taskbar and black titlebar produce a kind of letter-boxed effect, drawing your eyes toward the contents. We think it works pretty well. What we do is mix black in with the selected window color. If you look closely, you can see that your taskbar and maximized titlebars all have some of your window color mixed in.

The Complaints

Now, we have had a number of complaints from users on this one. It seems that people who bother to change their window color using the cool new Appearance control panel are not happy when their red or blue windows turn black. Of course, for any change we make there are a whole bunch of people who hate it. With 300 million users, even 1/10th of 1% of people don't like something, and only 1% of those REALLY don't like it, that is still thousands of people who will email us daily, blog about it, tell their friends, etc. The trick of working in Windows is to have a thick skin while still remaining sensitive to potentially serious issues.

For this issue, we talked about it internally for quite a while. Were people just reacting to the change? Would they get used to it over time and even grow to appreciate it? Or would it be one of those little annoying things that bugs people a little bit every day? We even considered whether or not this should be a choice for the user. Was it worth adding more UI to the system? And of course as time went on, the ability to make any change at all was going down by the day.

The Fix

In the end, we decided that we like the black and think it is the right thing to do, but we want to respect the user's color choice for users who bother to make a change. So - starting in today's build, we have significantly backed off the amount of black that is mixed in with the user's color for maximized windows. This is not particularly noticeable with the default color, but with the more intense colors like Red and Orange, you will appreciate the difference.

So - cheers for everyone who didn't like the black windows! And for those who want the darkness, just change your window color to something more black.

Source: shell:revealed

Link to comment
https://www.neowin.net/forum/topic/500646-ms-modifies-black-maximized-borders/
Share on other sites

Builds around Beta 2 exhibited a similar behaviour. I tinkered around colour/saturation/brightness scales to have my max windows show a hint of blue but all that changed a build or two before RC1. Guess it's nice to have that back, though the black doesn't bother me.

Nice that they did something about it, but seriously - is it that hard to just add a checkbox "Don't change border when maximized" ?

Than they could make everyone happy - not just "a little happy".

I think it's nice and logical like it is now, but i don't understand why they didn't make it optional, when they even spent time discussing what to do with it.

bah... so we still won't get transparency? we get frickin colorful background? EW....

seems that Windows Vista will be the version of Windows which will get me used to NOT maximizing windows...

thanks to Microsoft for changing it anyways. i guess i'll be able to make better judgement of it when i see screenies or the build itself.

What a bunch of whiny girls you people are...:blink:

The letterbox effect makes perfect visual and UI sense. :yes: (Y)

I agree. I think it looks cool when the window gets that smooth black border when maximized. I think it really doesn't matter...when the window is maximized, you don't need to and won't see the other windows, so what does it matter if the window border is different?

Stop being girly men! :schwarzeneggar:

bah... so we still won't get transparency? we get frickin colorful background? EW....

seems that Windows Vista will be the version of Windows which will get me used to NOT maximizing windows...

thanks to Microsoft for changing it anyways. i guess i'll be able to make better judgement of it when i see screenies or the build itself.

If you maximize a window you obviously want it to fill the screen, so what possible advantage is there to having a little transparency around the edges, distracting you from the content in the middle? That’s not what the transparency effects were intended for. It's pretty obvious and frankly simple common sense as to why they turned off that ability.

If you maximize a window you obviously want it to fill the screen, so what possible advantage is there to having a little transparency around the edges, distracting you from the content in the middle? That’s not what the transparency effects were intended for. It's pretty obvious and frankly simple common sense as to why they turned off that ability.

the point is: it simply changes the way that the entire UI was shown before to something different (from transparent windows and taskbar to totally opaque windows and taskbar) that is confusing enough for the user.

and it changes abruptly. IF Microsoft had put a maximize animation and while maximizing, it made the window more and more opaque, it'd be better, IMO.

even then, that solution is not good enough. after all, the color of the entire UI will change to something darker. which is just weird. the user will just go "this wasn't the color i chose back then. why did it change?"

i'm not talking about distraction or not. i'm talking about it doing things in a clunky way. which is exactly how i see the whole opaque maximized windows :s

edit: i don't know about other people. but i NEVER maximized a window to "focus" on one app... i always did it in order to get the most space available on my screen to that window... just that. not anything related to focusing or whatever. people still alt+tab like hell with maximized windows.

reminds me of how Windows Explorer deals with folders with different file types... it overrides my selections for how i want to view a folder. it's just stupid. (try selecting a folder, setting it to details, customizing the columns and then going to Tools > Options... and applying to all folders. and THEN visit a folder filled with pics.... or mp3 files.) not to mention the whole "Windows Explorer doesn't remember its size" thing...

Edited by Menge

Finally, one of the most bitched-about topics at shellrevealed is cured... partially.

I'm now perfectly fine with this decision. The amount of black when maximized WAS overkill. Hopefully now it won't be.

Every idiot who says MS doesn't listen from now on should be slapped in the face with a monitor displaying a maximized window in Vista.

But they didn't listen. The change they are talking about goes only part way to what Beta Testers and others have been asking. Also, does the taskbar still turn black when a window is maximised or does it behave the same as maximized borders?!

Just because Microsoft changes 1 of over three dozen odd behaviours in Aero - that doesn't suddenly make microsoft responsive.

But they didn't listen. The change they are talking about goes only part way to what Beta Testers and others have been asking. Also, does the taskbar still turn black when a window is maximised or does it behave the same as maximized borders?!

Just because Microsoft changes 1 of over three dozen odd behaviours in Aero - that doesn't suddenly make microsoft responsive.

I can't believe you still think they aren't doing their best. I want my window to be 6 inches thick and white. Joe Blow wants it completely transparent. MS can't listen to every beta tester and give them what they want. Did you even read the blog?

Who says MS has only changed one thing? :sleep:

I want my window to be 6 inches thick and white. Joe Blow wants it completely transparent. MS can't listen to every beta tester and give them what they want.

Sure they can. As pointed out, they could put a checkbox that completely disables the black maximize effect. Very simple and satisfies a lot of users.
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
    • The unified inbox, when it arrives, will be a powerful argument for those who have > 1.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!