Riley Langbein

That error usually implies there is something wrong with your path (in this case, ClientFeature in createServerFeature). However I've only seen it in collection level imports, not custom lexical features...

So it looks to be specific to how you have implemented your custom nodes. If I replace your custom node with the below: ``` export class ColorTextNode extends ElementNode {...

Glad you've found a workaround! Could you try importing it from '@payloadcms/richtext-lexical/lexical/utils' instead? It seems the isHTMLElement that you are referencing is different to the one used in the link...

I originally created that PR and I'm not against the idea of reverting it, I do agree it adds complexity. The reverted functionality can be revisited more broadly when we...

I have been unable to replicate this in v3.0.2 using postgres in the website template. ® in UTF-8 encoding would be `0xC2 0xAE`. Since in your case it is only...

I decided to look into this more and it's because Firefox and Safari do not support the [Sec-CH-Prefers-Color-Scheme](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Sec-CH-Prefers-Color-Scheme) header. Until there is support it's unlikely there is much we can...

The tailwindcss website takes a different approach to resolving this problem through the use of injecting a script tag into the head in their root layout file (https://github.com/tailwindlabs/tailwindcss.com/blob/main/src/app/layout.tsx). It's possible...

Appreciate the response @GermanJablo. You've got me thinking about how we can support keyboard users while still allowing the indent feature to be available by default. What are your thoughts...

Hi @GermanJablo, very much appreciate the feedback, I think we're on the path towards finding a solution that works for all users. I've updated my PR to allow for the...

Upon further investigation, this looks to be a firefox specific bug. Chromium browsers work as you would expect when pressing the escape key. With that in mind, I will explore...