The latest updates on your projects. Learn more about Vercel for Git ↗︎

@etrepum Would you know why marking the decorator node as inline does not actually work? Something is off with the selection bit.

I don't think it works inline because of the css, divs are display: block by default. The node itself is inline from lexical's perspective, it's more of a rendering concern.

To make it work with formatting you could make it not a decorator, it could be a TextNode subclass, although we don't currently have a selection/navigation mode by default that would treat a 'token' node as one unit as far as keyboard and pointer selection is concerned (I don't know how meta is using token mode, but maybe we could just fix that, or add a method or plugin to change that behavior for some or all token TextNode).

I don't think it works inline because of the css, divs are display: block by default. The node itself is inline from lexical's perspective, it's more of a rendering concern.

To make it work with formatting you could make it not a decorator, it could be a TextNode subclass, although we don't currently have a selection/navigation mode by default that would treat a 'token' node as one unit as far as keyboard and pointer selection is concerned (I don't know how meta is using token mode, but maybe we could just fix that, or add a method or plugin to change that behavior for some or all token TextNode).

I started with Element node initially, but the decorator just allowed for nice isolation of the component code with all the event listeners. I do agree, the node is closer to a mention or a hashtag with just a 'onclick' behaviour. I'll look into the CSS. Maybe we can get @zurfyx or @fantactuka to help with the 'token' part?

Just for information, here is the Clipboard HTML from Google Docs' @Today element:

<meta charset="utf-8">
<b style="font-weight:normal;" id="docs-internal-guid-8ead19bd-7fff-859b-a6a8-bd93d5d97918">
<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;">
<span style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;" data-rich-links="{&quot;dat_df&quot;:{&quot;fres_frt&quot;:1,&quot;dfie_ts&quot;:{&quot;tv&quot;:{&quot;tv_s&quot;:1754913600,&quot;tv_n&quot;:0}},&quot;dfie_l&quot;:&quot;en&quot;,&quot;dfie_p&quot;:{&quot;fres_frt&quot;:0,&quot;tres_tv&quot;:&quot;MMM d, y&quot;},&quot;dfie_dt&quot;:&quot;Aug 11, 2025&quot;,&quot;dfie_pt&quot;:3,&quot;dfie_tpt&quot;:0,&quot;dfie_tzi&quot;:&quot;&quot;},&quot;type&quot;:&quot;date&quot;}">Aug 11, 2025</span>
</p>
</b>
<br class="Apple-interchange-newline">

Will now Lexical be able to paste this HTML as DateTime Node?

Ha-ha, I'm still sad, no-one actually uses <time> for representing datetime semantics :)

Just for information, here is the Clipboard HTML from Google Docs' @Today element:

<meta charset="utf-8">

<b style="font-weight:normal;" id="docs-internal-guid-8ead19bd-7fff-859b-a6a8-bd93d5d97918">

<p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;">

<span style="font-size:11pt;font-family:Arial,sans-serif;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;" data-rich-links="{&quot;dat_df&quot;:{&quot;fres_frt&quot;:1,&quot;dfie_ts&quot;:{&quot;tv&quot;:{&quot;tv_s&quot;:1754913600,&quot;tv_n&quot;:0}},&quot;dfie_l&quot;:&quot;en&quot;,&quot;dfie_p&quot;:{&quot;fres_frt&quot;:0,&quot;tres_tv&quot;:&quot;MMM d, y&quot;},&quot;dfie_dt&quot;:&quot;Aug 11, 2025&quot;,&quot;dfie_pt&quot;:3,&quot;dfie_tpt&quot;:0,&quot;dfie_tzi&quot;:&quot;&quot;},&quot;type&quot;:&quot;date&quot;}">Aug 11, 2025</span>

</p>

</b>

<br class="Apple-interchange-newline">

Will now Lexical be able to paste this HTML as DateTime Node?

Ha-ha, I'm still sad, no-one actually uses <time> for representing datetime semantics :)

I'm currently on holidays. If you raise the PR, I'd be more than happy to review and merge 😃.