title bar should not be accent colour when window is inactive when accent coloured title bars are en

%3CLINGO-SUB%20id%3D%22lingo-sub-1927109%22%20slang%3D%22en-US%22%3Etitle%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20are%20en%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1927109%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fbugs.chromium.org%2Fp%2Fchromium%2Fissues%2Fdetail%3Fid%3D1084912%26amp%3Bq%3Daccent%2520title%2520bar%26amp%3Bcan%3D1%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E1084912%20-%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20are%20enabled%20-%20chromium%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efirefox%20gets%20it%20right...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1927515%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1927515%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319951%22%20target%3D%22_blank%22%3E%40pneenkoalabear%3C%2FA%3E%26nbsp%3BInteresting%2C%20maybe%20it's%20the%20design%20of%20Chromium.%20Does%20it%20happen%20in%20Chrome%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1929242%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1929242%22%20slang%3D%22en-US%22%3Eyep%20also%20happens%20in%20chrome%2C%20hence%20why%20I%20linked%20the%20Chromium%20bug.%20They%20also%20happen%20to%20be%20more%20responsive%20to%20feedback%20there%2C%20which%20is%20not%20necessarily%20a%20compliment%20as%20they%20are%20VERY%20VERY%20bad%20at%20listening%20to%20feedback.%20Something%20both%20Google%20and%20Microsoft%20have%20in%20common%20I%20guess...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930917%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930917%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319951%22%20target%3D%22_blank%22%3E%40pneenkoalabear%3C%2FA%3E%20Something%20ONLY%20Google%20has.%20Microsoft%20listened%20to%20everyone's%20feedback%20and%20now%20look%20at%20what%20we%20have!%20In%20Canary%2C%20MS%20is%20offering%20themes!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930924%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930924%22%20slang%3D%22en-US%22%3EI%20think%20Google%20at%20first%20was%20listening%20too%2C%20but%20then%20they%20got%20to%20a%20point%20where%20there%20wasn't%20any%20real%20competitor%20so%20they%20didn't%20care%20anymore.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930951%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930951%22%20slang%3D%22en-US%22%3Ebruh.%20themes%3F%20you%20realise%20Edge%20is%20just%20Chromium%2C%20right%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20could%20go%20on%20all%20day%20trying%20to%20explain%20that%20MS%20is%20just%20as%20bad%20as%20Google%20in%20terms%20of%20listening%20to%20us%20(dare%20I%20say%20even%20privacy%2FToS%20wise!).%20I%20could%20show%20you%20very%20real%2C%20easy%20to%20reproduce%20bugs%20in%20all%20sorts%20of%20MS%20software%20like%20Windows.%20I%20could%20show%20you%20all%20sorts%20of%20missing%20features%20across%20MS%20stuff.%20Some%20stuff%20is%20because%20they%20have%20their%20head%20in%20the%20sand%20(MSIX%2C%20WinUI%2C%20UWP...)%3CBR%20%2F%3E%3CBR%20%2F%3Ebut%20it's%20very%20difficult%20to%20convince%20you%20because%20you%20believe%20them.%20watch%20Explorer%20crash%20and%20say%20%22it's%20the%20future%22.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930977%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319951%22%20target%3D%22_blank%22%3E%40pneenkoalabear%3C%2FA%3EI'll%20watch%20Explorer%20crash%20and%20say%20%22it's%20the%20%3CSTRONG%3Epast%3C%2FSTRONG%3E%22%20because%20Edge%20never%20crashes.%20(FM)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1931130%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1931130%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F565232%22%20target%3D%22_blank%22%3E%40Kam%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F565232%22%20target%3D%22_blank%22%3E%40Kam%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3EOr%20Alt%2BShift%2BI%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EI'm%20not%20talking%20about%20Edge's%20feedback%2C%20I%20said%20feedback%20hub%20app%3C%2FP%3E%3CP%3Ethe%20shortcut%20is%20Win%20%2B%20F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1931194%22%20slang%3D%22en-US%22%3ERe%3A%20title%20bar%20should%20not%20be%20accent%20colour%20when%20window%20is%20inactive%20when%20accent%20coloured%20title%20bars%20ar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1931194%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20Windows%2010%20v20H2's%20integration%20with%20Edge%20is%20terribly%20buggy%3A%3C%2FP%3E%3CP%3EThe%20feature%20shows%20Edge%20tabs%20in%20alt%2Btab%2C%20not%20task%20view.%20task%20view%20is%20win%2Btab.%20Anyway%2C%20despite%20having%20turned%20that%20off%20in%20Windows%20Settings%2C%20it%20still%20causes%20Windows%20Explorer%20to%20crash%20(if%20you%20restore%20a%20*large*%20session%20for%20example)%20and%20sometimes%20a%20random%20Edge%20tab%20will%20pop-up%20as%20Windows%20Explorer.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20mentioned%20the%20rewritten%20task%20view%20to%20back%20my%20point%20that%20MS%20sucks%20(to%20say%20it%20succinctly).%20They%20abandoned%20timeline%20anyway%2C%20which%20was%20the%20whole%20point%20in%20rewriting%20task%20view.%20But%20they%20didn't%20revert%20to%20the%20old%20one%20after%20doing%20that.%20They%20tried%20to%20patch%20it%20up%20and%20even%20added%20new%20features%20to%20it.%20The%20task%20view%20that%20causes%20Explorer%20to%20restart.%20The%20task%20view%20that%20doesn't%20handle%20many%20windows%20well.%20Not%20even%20the%20window%20placement%20is%20very%20nice.%20I've%20experienced%20instabilities%2C%20performance%20issues%20and%20visual%20glitches%20with%20it%20across%20multiple%20devices%20and%20find%20it%20interesting%20that%20you%20two%20don't%20have%20such%20issues.%3CBR%20%2F%3E%3CBR%20%2F%3ESubmitting%20feedback%20to%20both%20edge%20and%20windows%20is%20a%20waste%20of%20time%20in%20retrospect.%20It's%20screaming%20into%20the%20void.%20But%20there%20are%20three%20FBH%20issues%20linked%20in%20that%20GitHub%20issue.%20Not%20a%20single%20one%20was%20even%20looked%20at%20by%20MS%2C%20then%20or%20now.%20They%20only%20look%20at%20and%20fix%20issues%20when%20they%20hit%20that%20repository.%20Proof%20that%20the%20FBH%20is%20a%20literal%20void.%20They%20even%20said%20it%20themselves%20in%20one%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3Ewell%20this%20was%20the%20essay%20i%20wanted%20to%20avoid%20lol%3C%2FP%3E%3C%2FLINGO-BODY%3E
27 Replies

@pneenkoalabear Interesting, maybe it's the design of Chromium. Does it happen in Chrome? 

That's right, in Windows explorer it is correctly applied but on Edge the color doesn't change whether active or inactive.
yep also happens in chrome, hence why I linked the Chromium bug. They also happen to be more responsive to feedback there, which is not necessarily a compliment as they are VERY VERY bad at listening to feedback. Something both Google and Microsoft have in common I guess...
@pneenkoalabear Something ONLY Google has. Microsoft listened to everyone's feedback and now look at what we have! In Canary, MS is offering themes!
I think Google at first was listening too, but then they got to a point where there wasn't any real competitor so they didn't care anymore.
bruh. themes? you realise Edge is just Chromium, right?

I could go on all day trying to explain that MS is just as bad as Google in terms of listening to us (dare I say even privacy/ToS wise!). I could show you very real, easy to reproduce bugs in all sorts of MS software like Windows. I could show you all sorts of missing features across MS stuff. Some stuff is because they have their head in the sand (MSIX, WinUI, UWP...)

but it's very difficult to convince you because you believe them. watch Explorer crash and say "it's the future".

@pneenkoalabearI'll watch Explorer crash and say "it's the past" because Edge never crashes. (FM)

@Kam 


@Kam wrote:
@pneenkoalabearI'll watch Explorer crash and say "it's the past" because Edge never crashes. (FM)

Edge has nothing to do with explorer. explorer is also called Windows explorer.

uh. you haven't opened task view have you. task view + 20H2+edge = explorer crash, one way or another. either stupid task view or stupid tab integration that doesn't actually turn off. (HotCakeX, see this message to understand what I meant in my previous message)

@pneenkoalabearDon't boss me around, I like MS, you like Google. And don't tell me that I haven't done anything. I have opened Task View a million times.

I can't really reproduce this, Windows 10 20H2 + Edge + task view open/close. any other steps ?
@HotCakeX He/She might mean that in task view he/she sees the number of tabs open. IMO that is never stupid.
i never bossed you around lol. i don't like google. i don't like microsoft. neither listen to us. i don't like apple either.

are you on a version of Windows higher than 1803? I'm not sure if you have the broken, rewritten task view. check out the WinDev issue on GitHub I linked above.
Thanks for the link, in these situations it's better to open a feedback in feedback hub app, record the problem using the built in tool and let it capture all the data it can, then share the feedback link in GitHub. since it happens randomly, I think that's the most useful way to share it with Windows team.