Conversation

Notices

1. Embed this notice
   cassidyclown (cassidyclown@clubcyberia.co)'s status on Friday, 22-May-2026 21:07:22 JST cassidyclown
   Which pleroma-fe version is working with latest firefox version and has the least AIDs? Thanks. :blobcatgrinch:
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:12 JST 

     in reply to

     • Phantasm
     @phnt @cassidyclown Digging around, it's some v3 themes bullshit as usual. Pre-v3 versions should work just fine.
     ✙ dcc :pedomustdie: :phear_slackware: likes this.
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Friday, 22-May-2026 21:07:13 JST Phantasm

     in reply to

     • 
     @mint @cassidyclown The issue is that Mozilla implemented some ::webkit CSS class functionality, but not all of it. There's an internal check in FE/Vue/something that checks whether some ::webkit class is supported and if it is, it uses some CSS settings from that class. Problem is that Mozilla implemented just enough for the check to pass, but not everything that is used and decided that when it encounters an unimplemented class, it should throw a syntax error instead of ignoring it. It's incredibly retarded.
     
     https://mastodon.social/ap/users/115667120638353806/statuses/116509834068625047
     https://shigusegubu.club/objects/1870c3cc-0dc7-4c81-b638-54174e671e29 (later in the thread)
     
     What's even more retarded is that originally the request for supporting the classes was rejected as wontfix years ago: https://bugzilla.mozilla.org/show_bug.cgi?id=1432935
   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Friday, 22-May-2026 21:07:13 JST Phantasm

     in reply to

     • 
     • Phantasm
     @mint @cassidyclown In other words, use ESR or Chrome/Webkit(-GTK). I don't know what is the first affected FE version by this Firefox bug, and neither does probably hj.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:14 JST 

     in reply to

     • 
     • Phantasm
     @cassidyclown @phnt was telling that Schmozilla broke something in latest release but I swear the screenshots I saw had that "uwu we made a fucky wucky" fluoride error page instead of just a blank page.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:15 JST 

     in reply to
     @cassidyclown Fucking weird. Since it works in Firefox ESR but apparently not on the bleeding edge niggercattle release, this might be a different bug.
   • Embed this notice
     cassidyclown (cassidyclown@clubcyberia.co)'s status on Friday, 22-May-2026 21:07:16 JST cassidyclown

     in reply to

     • 
     @mint haven't done anything?
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:17 JST 

     in reply to

     • 
     @cassidyclown Nevermind, you've already reverted.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:18 JST 

     in reply to

     • 
     @cassidyclown Actually he's on d7b1aaa61, you're on 83189d9d4. Shit broke between the two.
   • Embed this notice
     cassidyclown (cassidyclown@clubcyberia.co)'s status on Friday, 22-May-2026 21:07:19 JST cassidyclown

     in reply to

     • 
     @mint kf is apparently working so I assume latest version is working?
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:19 JST 

     in reply to
     @cassidyclown Could also be, though I'm not seeing any relevant commits in fe repo. Joah might've fixed it himself with claude copilot.
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:20 JST 

     in reply to
     @cassidyclown No, it's some chromium-exclusive CSS class that makes the page fail to load because JS macaques are unable to make functioning websites. Still gonig to an even older version suggested would indeed lower the amount of AIDS.
   • Embed this notice
     cassidyclown (cassidyclown@clubcyberia.co)'s status on Friday, 22-May-2026 21:07:21 JST cassidyclown

     in reply to

     • 
     @mint is that what's causing the issue with firefox? (mine is more recent than that and doesn't have the splash screen)
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 22-May-2026 21:07:22 JST 

     in reply to
     @cassidyclown Whatever one from before they introduced the splash screen, 2cddc138e is probably a safe bet.