Home

White text overlay bug fixed in build 76.0.159.0

%3CLINGO-SUB%20id%3D%22lingo-sub-566436%22%20slang%3D%22en-US%22%3EWhite%20text%20overlay%20bug%20fixed%20in%20build%2076.0.159.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566436%22%20slang%3D%22en-US%22%3E%3CP%3EStarting%20with%20build%2076.0.151.0%2C%20there%20was%20a%20bug%20that%20screwed%20up%20the%20display%20of%20white%20text%20overlayed%20a%20darker%20colour.%20I%20can%20attest%20that%20it%20has%20been%20fixed%20for%20me.%20Should%20anybody%20here%20still%20have%20problems%2C%20I%20suggest%20you%20bring%20up%20the%20bug%20again%20with%20Microsoft%20and%20tell%20them%20it%20isn't%20fixed%20for%20everybody.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-566550%22%20slang%3D%22en-US%22%3ERe%3A%20White%20text%20overlay%20bug%20fixed%20in%20build%2076.0.159.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566550%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316442%22%20target%3D%22_blank%22%3E%40NicolSD%3C%2FA%3E.%26nbsp%3B%20Just%20curious%2C%20did%20you%20report%20this%20issue%20via%20the%20In-app%20feedback%3F%26nbsp%3B%20If%20so%2C%20did%20you%20receive%20and%20email%20telling%20you%20that%20the%20issue%20was%20fixed%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EElliot%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-566589%22%20slang%3D%22en-US%22%3ERe%3A%20White%20text%20overlay%20bug%20fixed%20in%20build%2076.0.159.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566589%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3BYes%20and%20no.%20Yes%2C%20I%20reported%20it%20through%20the%20in-app%20Mr.%20Smiley.%20But%20no%2C%20like%20every%20other%20bug%20so%20far%2C%20I%20haven't%20been%20notified%20that%20it%20had%20been%20fixed.%20I%20have%20been%20testing%20the%20bug%20again%20and%20again%20with%20every%20build%20until%20it%20finally%20worked.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou'll%20remember%20that%20I%20have%20reported%20bugs%20fixed%20in%20the%20past.%20This%20is%20not%20the%20first%20time%20I%20have%20done%20this.%20However%2C%20not%20once%20have%20I%20been%20notified%20by%20Microsoft%20that%20the%20bugs%20were%20fixed.%2C%20I%20had%20to%20find%20out%20for%20myself.%20For%20example%2C%20the%20two%20Facebook%20bugs.%20They%20are%20definitely%20fixed%20but%20they%20were%20never%20recognized%20as%20having%20ever%20existed%20let%20alone%20fixed%20in%20any%20of%20the%20Dev%20notes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20is%20what%20bugs%20me%20about%20your%20Insider%20system.%20We%20are%20kept%20in%20the%20dark!%20I%20submitted%20as%20detailed%20a%20report%20as%20I%20could%20about%20the%20white%20text%20overlay%20bug.%20I%20got%20the%20standard%20email%20acknowledging%20that%20my%20report%20had%20been%20received.%20And%20that%20was%20it.%20I%20never%20heard%20again%20from%20Microsoft.%20I%20checked%20and%20checked%20if%20the%20bug%20was%20still%20there%20after%20every%20build%20until%20today.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20add%20to%20the%20frustration%2C%20the%20bug%20is%20not%20going%20to%20be%20recognized%20as%20having%20ever%20existed%20in%20the%20upcoming%20Dev%20notes.%20How%20can%20I%20say%20that%3F%20Because%20that's%20what%20MS%20does%20all%20the%20time.%20The%20two%20Facebook%20bugs%20were%20never%20acknowledged%20as%20existing%20or%20having%20been%20fixed.%20The%20same%20thing%20is%20going%20to%20happen%20with%20this%20bug.%20The%20bug%20started%20with%20build%2076.0.151.0.%20I%20reported%20it%20and%20have%20been%20checking%20it%20with%20every%20build%20since.%20Today%2C%20the%20bug%20is%20gone.%20I%20know%20it%20was%20somehow%20fixed.%20I%20also%20know%20that%20I'll%20never%20hear%20back%20from%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20is%20why%20we%20(I%20am%20certain%20I%20am%20not%20alone%20in%20this)%20want%20a%20proper%20report%20of%20existing%20and%20fixed%20bugs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20now%20that%20I've%20let%20off%20steam%2C%20I%20feel%20better.%3C%2FP%3E%3C%2FLINGO-BODY%3E
NicolSD
Regular Contributor

Starting with build 76.0.151.0, there was a bug that screwed up the display of white text overlayed a darker colour. I can attest that it has been fixed for me. Should anybody here still have problems, I suggest you bring up the bug again with Microsoft and tell them it isn't fixed for everybody.

2 Replies

Thank you @NicolSD.  Just curious, did you report this issue via the In-app feedback?  If so, did you receive and email telling you that the issue was fixed?

 

Thanks,

Elliot

@Elliot Kirk Yes and no. Yes, I reported it through the in-app Mr. Smiley. But no, like every other bug so far, I haven't been notified that it had been fixed. I have been testing the bug again and again with every build until it finally worked.

 

You'll remember that I have reported bugs fixed in the past. This is not the first time I have done this. However, not once have I been notified by Microsoft that the bugs were fixed., I had to find out for myself. For example, the two Facebook bugs. They are definitely fixed but they were never recognized as having ever existed let alone fixed in any of the Dev notes.

 

That is what bugs me about your Insider system. We are kept in the dark! I submitted as detailed a report as I could about the white text overlay bug. I got the standard email acknowledging that my report had been received. And that was it. I never heard again from Microsoft. I checked and checked if the bug was still there after every build until today.

 

To add to the frustration, the bug is not going to be recognized as having ever existed in the upcoming Dev notes. How can I say that? Because that's what MS does all the time. The two Facebook bugs were never acknowledged as existing or having been fixed. The same thing is going to happen with this bug. The bug started with build 76.0.151.0. I reported it and have been checking it with every build since. Today, the bug is gone. I know it was somehow fixed. I also know that I'll never hear back from Microsoft.

 

That is why we (I am certain I am not alone in this) want a proper report of existing and fixed bugs.

 

And now that I've let off steam, I feel better.