Paste and General Rich Text UX issues

Problem 1: Paste in a Rich Text cell does not work

Steps to reproduce:

  1. Navigate over the table to a simple text cell containing some text value with the arrow keys,
  2. Press Cmd+C to copy,
  3. Navigate to a Rich Text cell with the arrow keys,
  4. Press Cmd+V,
  • Expected: The copied text is pasted into the Rich Text cell.
  • Actual: Rich Text cell is unchanged, the warning toast “cannot paste” is displayed.

Problem 2: When the Rich Text editor opens, the entry point is not focused

Steps to reproduce:

  1. Click an empty RTF cell - the editor view appears

  • Expected: The text area is focused, and the user can type.
  • Actual: Typing a text is not accepted because the entry point is not focused. The user has to click the text area.

Problem 3: Cannot enter the Rich Text editor with keys only

Steps to reproduce:

  1. Navigate to a Rich Text cell with the arrow keys,
  2. Press F2 or Space
  • Expected: The Rich Text editor appears to change the cell value.
  • Actual: On F2, nothing happens. On Space, the Entity Editor appears instead.

Problem 4: After making changes in the Rich Text editor, the record does not reflect the changes

Steps to reproduce:

  1. Enter the Rich Text editor and make changes,
  2. Exit with the Close cross or Back button,
  • Expected: The respective Rich Text cell to have the new value,
  • Actual: The cell remains unchanged.

Screen recording:

Unfortunately, I cannot upload video attachments here; therefore, here is the file:

Environment:

  • Fibery for Mac 2.8.5
  • macOS: 26.2 (25C56)
2 Likes

Unfortunately most of these bugs are not bugs from Fibery perspective, but side effects of Rich Text field implementation.

Problem 1. Not a bug, What you see in table is a snippet, not the full field, and it is not possible to paste here

Problem 2. A bug

Problem 3. Not a bug

Problem 4. Not a bug, since it may take time to sync rich text snippet with actual rich text

Thanks for your reply and for the ongoing efforts on this excellent product!

It’s great that most of the points are not bugs :smiling_face: I’ll add some context:

1. Paste operation is working for all other field types. Consistency would be appreciated.

Also, the warning toast text could be reworded for clarity. Currently, it’s a bit misleading: ”Can’t paste, Cannot create entity of “Personal/Journal” DB with missing required fields: Date” - But I didn’t mean to create an entity, nor did I have anything to do with the Date field. I just wanted to paste some text.

3. No, it’s not a bug. It’s an accessibility concern and a UX inconsistency. Many keyboard-first users would appreciate better hotkey support, such as using F2 or Enter to edit or toggle in-place editor, as is common in grid-based apps.

4 . I understand. Could we implement optimistic updates so that the user can see the changes being saved?

Accessibility and user experience are priorities that extend beyond core functionality. Nevertheless, a quick note tool is expected to work as smoothly as possible.

1 Like

So this may be one of the most helpful ux improvements if fixed.
This maybe not a bug, but its certainly an issue, that annoys (new) users.

This is actually a very frequent need i have for managing and inserting content.
E.g. common use case:

ChatGpt, please give me a table with 50 tasks for this project, with name and description. (or 50 articles with name and body)

but then..

  • Manually copy pasting into a table view is not possible.
  • Workaround with helper text field and automation is not possible - text field is limited in characters
  • Importing process is a time consuming process, only admins do that for large sets

..so there is currently no real solution

1 Like

Did you consider asking Fibery AI to do this, rather than asking an external AI and copy-pasting?

Yes I know, but Fibery AI is currently too restricting (model selection, token sizes, chat length, schema size) for me at this point.
But yes, if Fibery AI becomes more mature like an agentic system that would be ideal (I suggested that for the 2026 strategy).

Also about rich text. I feel like bit-rate got issues when size of text expands. I have a lot of long conversations just with text. It extremely lag and slow when opening or navigating in that text field