Feature/widget placement improvements

[crustytaco]

Description

• Added the Text Widget Editor overlay plus a Rich Text Editor toolbar for Notes, Message, and Custom Text widgets, including sanitation utilities and snippet support.
• Updated widget components, UI context, and data models so rich-text HTML is saved safely, with a refreshed Widget Font Settings modal for consistent typography controls.
• Improved the widget settings flyout: it now clamps to the viewport, shows plugin-specific settings for non-Text/Code widgets via [PluginContainer]

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Translation update

Changelog Entry

Added a full-featured rich text editor for text-based widgets, expanded widget settings persistence, and refreshed widget/fon`t settings UI with viewport-aware positioning.

Screenshots

Included in issue discussion / PR comment thread (dashboard widget settings flyout + font settings modal).

Related Issues

#70

Checklist

• Tested in development environment
• Tested in Firefox
• Tested in Chrome/Edge
• Added or updated unit tests (if applicable)
• All new and existing tests passed
• I have added a changelog entry
• I ran npm run translations
• This PR is ready to be merged

[sourcery-ai]

Sorry @crustytaco, your pull request is larger than the review limit of 150000 diff characters

[BookCatKid]

Hey. Thanks for opening this PR.

I know this was something you originally built for your own use, and I appreciate you taking the time to turn it into a PR. With that said, the current version is extremely large and introduces a lot of things at once, which makes it tough to review and merge into the project.

The core idea of having an edit mode that can be turned on and off is solid and something that could work really well in TablissNG. The problem is that the implementation here is much more complex than we need, and the overall style does not match the rest of the application. It uses a very futuristic look with a lot of heavy effects, and it ends up clashing with the existing simplistic design.

If you want, we can figure out a more focused version that keeps the good parts and fits the project more cleanly. Let me know how you want to move forward.

[BookCatKid]

@crustytaco Just making sure you see this. No pressure! :)

[crustytaco]

Hello!!! Absolutely! I am removing all the bells and whistles to match the current styles! :) did we want to keep the text and code editor popouts as well?

[BookCatKid]

Hello!!! Absolutely! I am removing all the bells and whistles to match the current styles! :) did we want to keep the text and code editor popouts as well?

Thanks! You can keep the text and code editors if you want. We'll see how it turns out, then decide. i'm not sure how else we would be able to edit text inside "edit mode", so TLDR yes lol.

[BookCatKid]

@crustytaco No pressure, but any progress?

[BookCatKid]

Hey @crustytaco, I'm going to close this pr for now because of inactivity, but feel free to ping me/re-open it!

[crustytaco]

Hey @crustytaco, I'm going to close this pr for now because of inactivity, but feel free to ping me/re-open it!

Hey! Sorry, been working around the clock on a project for work haha. I'll definitely reopen it as soon as i'm finished!

[crustytaco]

Hello! @BookCatKid I've nearly completed the edits! Are we able to reopen this? :)

[BookCatKid]

I don't see any new commits, but sure!

[BookCatKid]

Please merge main and resolve merge conflicts. Good luck with that 🫡

[sourcery-ai]

New security issues found

[crustytaco]

Latest commit was cleanup/follow-up work:

• Fixed widget settings prop/type errors by adding the missing defaultData handling.
• Cleaned up related formatting/type issues.
• Updated the FormatJS command resolution to use the local @formatjs/cli binary.
• Re-ran translations after the changes.

The earlier Sourcery security review threads are resolved/outdated after the DOMPurify rich-text sanitization updates. This should be ready for re-review.

[crustytaco]

Hello! Sorry for the extra updates here. I realized I needed to clean up a couple of translation items, and then the branch had a pnpm-lock.yaml conflict after upstream changed, so I merged the latest main and regenerated the lockfile.

[crustytaco]

All checks are passing now, and the react-markdown dependency issue has been fixed in the latest commit. This should be ready for maintainer review/merge when you have a chance.