Compiler explorer (godbolt.org) is not fully unbroken

[dinosaur]

With PM 34.0, the WeakRef support does allow Compiler explorer's page to load, but sadly it is now suffering from an issue I did not have in the (distant) past with PM (before the WeakRef usage by godbolt.org).

The text for the editors does not render at all for me and yes, I tried the site settings and changed the fonts family for others, to no avail (I also tried and excluded bitmap fonts from fontconfig). I of course tried the site's various themes, editor lines colouring options, etc, but still no joy. Finally, setting "javascript.options.weakrefs" to true does not change a thing.

Here is what I get (from a blank PM profile):

godbolt.png

There is no error reported in the error console, not even a warning...

Any idea ?

[jobbautista9]

Works fine for me in Windows 11 x64, both in my usual profile and a fresh one of 34.0.1.

[vannilla]

Does not work for me on Linux.

[adoxa]

FWIW it's also fine with 64-bit Basilisk (2026.01.23; usual profile), Win10.

[Moonchild]

Looks fine for me as well on x64 Win 10

[vannilla]

There is a transform: translate3d(0px, 0px, 0px) CSS directive that "hides" the text content, but apparently it behaves as expected only on Windows.

[dinosaur]

There is a transform: translate3d(0px, 0px, 0px) CSS directive that "hides" the text content, but apparently it behaves as expected only on Windows.

Well spotted !

I managed to make the site work thanks to the Stylem extension, with the following override:

Code: Select all

@-moz-document domain("godbolt.org") {
  html body.enable-motion div#root div.lines-content.monaco-editor-background
  {
    transform: revert !important;
  }
}

But of course, it would be best to find the bug causing this issue under Linux and not Windows...

[Moonchild]

There is a transform: translate3d(0px, 0px, 0px) CSS directive

I have to wonder: Why on earth would they use a transform like that? It does literally nothing. Is this to try and work around bad font rendering in Chrome or something?

EDIT: Oof. oh wow. what on earth are they doing? This almost feels like deliberate breakage. I can see this CSS being all sorts of broken on some engines or causing absolutely massive resource/performance issues.

Code: Select all

position: absolute;
overflow: hidden;
width: 1.67772e+7px;
height: 1.67772e+7px;
transform: translate3d(0px, 0px, 0px);
top: 0px;
left: 0px;

This seems to be geared towards very very specific quirks. Look at that width and height. Then marking overflows hidden (so effectively creating a very large surface that would get hidden) and then doing that transform on the huge surface but all being 0 px. None of that would have a visual effect at all but can absolutely break things.

[UCyborg]

What about right-click context menu on the text area? It doesn't show. Maybe related to weird CSS?

[vannilla]

What about right-click context menu on the text area? It doesn't show. Maybe related to weird CSS?

The context menu is replaced by a custom one through Javascript and it seems whatever error is generated is swallowed whole and never printed in the console.
Unfortunately, the site's panels are managed by a package developed by Microsoft, so the chances of things improving are basically zero and all we can hope for is that through fixing web compat issues on other sites, eventually this one is caught too.
In the meantime, if you need the standard context menu while clicking inside one of the panels, you can hold the shift key to bypass the custom functions (I think this is intentional behaviour).

[dinosaur]

In the meantime, if you need the standard context menu while clicking inside one of the panels, you can hold the shift key to bypass the custom functions (I think this is intentional behaviour).

There's also a check box in the site settings menu to disable the custom context menu: I'm using this...

[Basilisk-Dev]

This issue does not affect MacOS. Works fine here.

[Veit Kannegieser]

https://godbolt.org/noscript works fine.

[Moonchild]

https://godbolt.org/noscript works fine.

Not like that is in any way comparable, of course.

[dinosaur]

I managed to make the site work thanks to the Stylem extension, with the following override:

Code: Select all

@-moz-document domain("godbolt.org") {
  html body.enable-motion div#root div.lines-content.monaco-editor-background
  {
    transform: revert !important;
  }
}

As of today, I had to change the override to something more generic (i.e. not restricted to enable-motion CSS path), with:

Code: Select all

@-moz-document domain("godbolt.org") {
  html div.lines-content.monaco-editor-background
  {
    transform: revert !important;
  }
}

The breakage keeps evolving over time...