Cannot copy one line of CSS in Firefox Dev - returns unicode token

​@ksn amazing, hope it will get fixed soon, its pretty time consuming to copy everything and delete what you dont need :(

Do you only have the issue on Firefox Dev? I’m now seeing it on regular Firefox as well (Firefox 142.0 on macOS 15.6). Same thing on a colleague’s computer (regular Firefox on macOS).

Same issue on Firefox 142.0 on Windows 11. I assume that all Firefox users should be affected then.

Hello ​@Aloïs Guichard and everyone following along — Tom here, stepping in for ​@ksn to acknowledge your report. Thanks for surfacing this. 🙏🏻

I’ve shared the browser details you provided with our engineering team, and I can confirm this issue is still on their radar. I don’t have a specific timeline for a resolution yet, but I’ll return to this thread as soon as I have more context or updates to share. Appreciate your patience in the meantime, and please keep us posted if you notice any changes on your side.

Thank you ​@Tom Reem! Yes, it will be great when it’s updated - we’re coming up on some heavy implementation time, so it will be used a lot.

(And apologies ​@Aloïs Guichard  - still wasn’t seeing multiple updates - I only use Firefox Dev, so hadn’t checked the regular version -- ty for doing so!)

Appreciate you letting me know, ​@J.S — I don’t have any new updates to share just yet, but I want to reassure you this is still flagged with our engineering team. We’re keeping an eye out for reports like yours, and I’ll reach back out as soon as I hear more.

Hi ​@Tom Reem  - fwiw, I’ve seen some additional issues/bugs in Firefox Dev (should be = Firefox regular):

• Compare Changes in Ready for Dev not loading content (works in Chrome) - just white wheels spinning (screenshot below)
• When logging in to the desktop app, app triggers Browser to log in, then browser shows a button to reopen and log into the desktop app - that button doesn’t work in Firefox (which means unable to use the desktop app until change default browser).

Hope all is well - and ty again!

Hi ​@J.S — thanks so much for flagging this and for including the screenshot. I’ve passed this along to the engineering team so they can take a closer look.

I don’t have any updates to share just yet, but they’re aware of what’s happening and reviewing it. Really appreciate you taking the time to surface this one.

This seems to be it. Thank you ​@Vsevolod Kochnev !

Had to add Figma as an exception. 

A little concerning, though - only Standard protections are on, nothing robust or extraordinary, doesn’t seem like this should be happening.