https://issues.dlang.org/show_bug.cgi?id=21241

Jon Degenhardt <jrdemail2000-dlang@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jrdemail2000-dlang@yahoo.co
                   |                            |m

--- Comment #1 from Jon Degenhardt <jrdemail2000-dlang@yahoo.com> ---
Renders fine for me using Chrome on MacOs (version 85.0.4183.102) and iPhone
IOS (version 85.0.4183.92).

--

https://issues.dlang.org/show_bug.cgi?id=21241

Seb <greeenify@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greeenify@gmail.com

--- Comment #2 from Seb <greeenify@gmail.com> ---
@Walter: this looks more like an issue with your browser. What version are you using? Does the flickering still appear after an upgrade to the latest version?

--

https://issues.dlang.org/show_bug.cgi?id=21241

Manu <turkeyman@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |turkeyman@gmail.com

--- Comment #3 from Manu <turkeyman@gmail.com> ---
Fine for me on windows.

--

https://issues.dlang.org/show_bug.cgi?id=21241

--- Comment #4 from Walter Bright <bugzilla@digitalmars.com> ---
>From the "About Chrome" page:
---
Google Chrome is up to date
Version 85.0.4183.102 (Official Build) (64-bit)
---

I'm running on 64 bit Win7.

I've had zero issues before with anything on the dlang web site.

--

https://issues.dlang.org/show_bug.cgi?id=21241

--- Comment #5 from Walter Bright <bugzilla@digitalmars.com> ---
Created attachment 1804
  --> https://issues.dlang.org/attachment.cgi?id=1804&action=edit
Chrome's rendering of the changlog

A picture is worth 1000 words.

--

https://issues.dlang.org/show_bug.cgi?id=21241

--- Comment #6 from Walter Bright <bugzilla@digitalmars.com> ---
Scrolling up and down creates completely erratic rendering.

--

https://issues.dlang.org/show_bug.cgi?id=21241

Ethan Watson <gooberman@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gooberman@gmail.com

--- Comment #7 from Ethan Watson <gooberman@gmail.com> ---
Exact same version of Chrome. Windows 10. No problems.

Whenever Chrome has a problem rendering a page, there's usually two things that cause it:

1) Plugins
2) Rendering options

The problem as described does sound similar to an option that Chrome enabled silently under the hood for me a year or two ago. Couldn't tell you what.

Either way, this is clearly a user-support issue for Chrome and not a fault with the document itself.

--

https://issues.dlang.org/show_bug.cgi?id=21241

--- Comment #8 from Walter Bright <bugzilla@digitalmars.com> ---
(In reply to Ethan Watson from comment #7)
> Either way, this is clearly a user-support issue for Chrome and not a fault with the document itself.

I've never seen this behavior before. It does not happen with other dlang.org pages. It does not happen with any other web site I visit.

That makes it a fault with the document, even if it is a fault with Chrome.

I understand that it's really, really hard to debug a problem that one cannot reproduce. But it's still a bug, and this will be here when the next person sees it, too.

--

https://issues.dlang.org/show_bug.cgi?id=21241

--- Comment #9 from Ethan Watson <gooberman@gmail.com> ---
(In reply to Walter Bright from comment #8)
> I've never seen this behavior before.

I have. I said that I have. I have personally seen exactly the behavior you screenshotted on my computer. Years ago, because of Chrome settings.

Even a cursory google with a few terms related to your problem will bring up pages as recently as June and as early as seven years ago.

Disable all your extensions and try again. Turn off GPU rendering and try again. Something in there is broken, not the page.

--

https://issues.dlang.org/show_bug.cgi?id=21241

--- Comment #10 from Walter Bright <bugzilla@digitalmars.com> ---
(In reply to Ethan Watson from comment #9)
> Disable all your extensions and try again. Turn off GPU rendering and try again. Something in there is broken, not the page.

I understand that. My point isn't that this page not rendering is a problem for me. It is a problem for our users. They're not going to google it, they're going to think "dlang has a crappy web site that doesn't render properly".

This kind of thing is something I've faced for 35 years. Being a small operation, I'd get blamed even when the problem was clearly with the much larger operation. I'm forced to work around the bugs in those larger operations. It simply doesn't matter that we're right and Chrome is wrong. The page doesn't work and so we are wrong.

If dlang.org had 1 million users, *then* Chrome would be wrong.

--