Claude for Chrome | slacker news

1. coffeecoders ◴[26 Aug 25 19:14 UTC] No.45030911[source]▶

Not sure if its only me, but most of the texts in this page aren't showing up.

https://i.imgur.com/E4HloO7.png

replies(9): >>45030973 #>>45031045 #>>45031198 #>>45031219 #>>45031224 #>>45031348 #>>45031387 #>>45031429 #>>45031440 #

2. iammjm ◴[26 Aug 25 19:19 UTC] No.45030973[source]▶

>>45030911 (TP) #

Yes, it’s broken

3. rafram ◴[26 Aug 25 19:24 UTC] No.45031045[source]▶

>>45030911 (TP) #

They say a picture is worth a thousand words.

(It's not even a font rendering issue - the text is totally absent from the page markup. I wonder how that can happen.)

4. latexr ◴[26 Aug 25 19:34 UTC] No.45031198[source]▶

>>45030911 (TP) #

It’s not only you. I tested in three different web browsers, each with their own rendering engine (Webkit, Chromium, Gecko), and all of them show no text. It’s not invisible, it’s plain not there.

Did they tell their AI to make a website and push to production without supervision?

5. hotfixguru ◴[26 Aug 25 19:35 UTC] No.45031219[source]▶

>>45030911 (TP) #

Same for me, Safari on an iPhone.

6. Nizoss ◴[26 Aug 25 19:36 UTC] No.45031224[source]▶

>>45030911 (TP) #

Same issue here, dark mode on mobile.

7. solardev ◴[26 Aug 25 19:42 UTC] No.45031348[source]▶

>>45030911 (TP) #

It's Web 4.0. You're supposed to bring your own GPT and let it make up the text as you go.

8. jampa ◴[26 Aug 25 19:45 UTC] No.45031387[source]▶

>>45030911 (TP) #

The blog works for me: https://www.anthropic.com/news/claude-for-chrome

9. vunderba ◴[26 Aug 25 19:48 UTC] No.45031429[source]▶

>>45030911 (TP) #

I don't know if this site was built by dogfooding with their own agents, but this just outlines a massive limitation where automated TDD doesn't come close to covering the basic question "does my site look off?" when vibe coding.

10. nzach ◴[26 Aug 25 19:49 UTC] No.45031440[source]▶

>>45030911 (TP) #

I've got the same error on my side. At first I thought it was some weirdness with Firefox, but opening on Chrome gives the same result.

I don't know what causes this bug specifically, but encountered similar behavior when I asked claude to create some frontend for me. It may not even be the same bug, but I find it an interesting coincidence.