Jun 20 2019 09:55 AM
Jun 20 2019 09:55 AM
Bug encountered while reading articles from Yahoo.com. While scrolling down to read article or comments, ads and images will move from their normal location on the right side, into the main content area where it obscures article content.
Jul 02 2019 07:39 AM
Jul 11 2019 12:33 PM
@madman370 I acknowledge it's difficult to know what state different bugs are in. This one is active and is assigned to a developer, but it has not yet been debugged. I am able to repro this in Chrome Canary as well, so there is a fundamental layout issue going on here.
Jul 24 2019 09:02 AM
As of 7/24/2019 the problem still exits. I know you have a developer working on this and we appreciate that. This problem did not exist prior to some point in June. What changed at that point? Just thinking (writing) out loud hoping that this might point to something to look into.
Aug 23 2019 12:20 PM
I've been gone a few weeks so I just had a chance to try out the Beta version. It's broke there too so I think if I stick with the Dev version I'm more likely to see it fixed there first as updates are done more frequently. Again, thanks for the update and I do like the product. Just a little annoying with this little glitch.
Sep 05 2019 12:08 PM - edited Sep 05 2019 12:16 PM
@johnjansen Sorry to keep hijacking this thread. Maybe I should start my own post but unless advised to do so, I'll stick to posting here.
Anyway, as of 9/5 this problem hasn't been fixed for the new Edge. I'm not sure how long it's been happening there, but when using the Chrome browser today on my Lenovo table, the same problem with the pictures jumping from the right to the left and covering the text in Yahoo is happening there too! To the best of my knowledge this wasn't happening before. I don't use Chrome on my PC but I checked and the same problem is there also.
Maybe your developer should work with them to solve this problem sooner, or if Chrome fixes the problem first, find out what they did.
Sep 05 2019 01:24 PM
Hi @Flyer11, What this means is that the bug in the Chromium code base that has been causing this issue on Microsoft Edge, has finally made it through the Chrome channels all the way to Stable. There is a pretty good chance that both Chromium and Microsoft developers are trying to understand this issue. When the bug is found and the fix is checked in, it will first go into Chromium, and then we will merge it into the Edge codebase, and release it first into Canary. Within a week or two it should be available in the Developer channel, and several weeks later, Beta. A very similar process will be taking place in the Chrome channels, with roughly the same timeline. Thanks - Elliot