Jan 29 2020 12:40 AM - edited Jan 29 2020 12:45 AM
I'm having a weird rendering issue. When I first opened the wiki page everything just load as fine but when I change to other tab and return there is certain parts of texts is scrambled.
When I highlighted the texts in question then everything back to normal. But if I change tab and return again the same sections will be scramble again.
I gonna ask is there anyone with similar issue?
Jan 29 2020 12:52 AM - edited Jan 29 2020 12:53 AM
I just checked your Wikipedia page:
https://en.wikipedia.org/wiki/Passenger_rail_terminology
on
Version 79.0.309.71 (Official build) (64-bit).
and
Version 81.0.407.0 (Official build) canary (64-bit)
couldn't reproduce that text distortion bug. could it be that a rogue flag is causing it?
has it happened on any other web pages?
Jan 29 2020 01:03 AM - edited Jan 29 2020 01:10 AM
Just now I thought it is a one time issue, guess I'm wrong.
I reopened the browser and open two wiki page that I had issue previously.
I will reply when I check others page.
FYI: Microsoft Edge Dev 81.0.403.1 (64-bit)
Jan 29 2020 01:19 AM
Jan 29 2020 08:06 AM
Jan 29 2020 08:09 AM
lol I find it funny, i mean how can it only happen on train related articles, that's like such a big coincidence, or maybe some alien species are trying to communicate with us through an advanced form of language.
I could reproduce it on the same Dev version, happens randomly though, needed to close/reopen Edge dev a few times to make it happen again
Jan 31 2020 11:16 AM
Jan 31 2020 11:32 AM
Feb 03 2020 11:52 AM
I've been seeing the same thing. It seems like it can happen on any web page, a small string of text will suddenly appear as garbage. I thought at first that it might be a video card issue, maybe bad memory causing garbage output on a section of the screen, but then found that it's happening on my laptop as well as my desktop, and only on web pages, not in other apps. Must be something in the current Edge dev build.
For reference, I'm seeing this on Version 81.0.403.1 (Official build) dev (64-bit)
Feb 03 2020 12:03 PM
Here's a (redacted) screenshot showing an example I had a few minutes ago. This was taken while I was viewing the message headers of an email on outlook.office.com.
On the second line, the C after my redaction is a real character that appears as it should, the garbage begins immediately after that.
Feb 05 2020 02:09 PM
I'm also seeing corrupted text, in my case in almost every Word document I open in the web app. Verified it's still present in today's update (81.0.410.1)
Feb 05 2020 07:12 PM
Solution@Bruce_Lowekamp @Steve Whitcher @Limyx826
"the visual glitch is completely random and not caused by any user actions, although highlighting the text should fix it (at least until it happens again). It's caused by an upstream Chromium bug, and we received the fix for it from them earlier this week, so it should make it into the next Dev release."
Feb 06 2020 10:46 AM
@HotCakeX, @Limyx826, @Bruce_Lowekamp @Steve Whitcher : Thank goodness it's fixed. I was also worried it might be a hardware issue. So far, no more scrambled text on Dev 81.0.410.1.
Feb 06 2020 10:56 AM
@Mike Glenn I have scrambled text on this version. It is probably not included?
Feb 06 2020 11:18 AM - edited Feb 06 2020 11:20 AM
@VladislavKosev, looks like I jumped the gun. I just read through the 81.0.410.1 is live post and realized the fix hasn't been released yet. I updated to Dev to 81.0.410.1 and rebooted this morning. I haven't seen scrambled text all day so far, whereas it was happening frequently last night.
Out of curiosity, have you rebooted since noticing the scrambled text? It'll be interesting to see how long I can go before seeing the glitch again.
Feb 06 2020 11:21 AM
@Mike Glenn, I did update this morning, but haven't rebooted. You think rebooting somehow relate to the problem? Had scrambled text just 10 minutes ago.
Feb 06 2020 11:28 AM
No rebooting is fine. the problem is within Chromium codes.
Feb 05 2020 07:12 PM
Solution@Bruce_Lowekamp @Steve Whitcher @Limyx826
"the visual glitch is completely random and not caused by any user actions, although highlighting the text should fix it (at least until it happens again). It's caused by an upstream Chromium bug, and we received the fix for it from them earlier this week, so it should make it into the next Dev release."