- What does mdobes/rich-editor-fullscreen actually do?
- It adds a fullscreen toggle to the toolbar of Filament V4's Rich Editor so you can write and edit long-form content on an expanded, distraction-free canvas without leaving the form. It is purely a presentation-layer extension: the editor still produces Filament's normal HTML or JSON payload, and fullscreen is only a viewport concern. It does not touch your domain model, persistence, or content serialization.
- How do I install and register it in a Laravel app?
- Install it with composer require mdobes/rich-editor-fullscreen, then register the plugin in the plugins([]) array of the relevant PanelProvider. Some per-field opt-in may also be available depending on how the package exposes its API. Integration effort is measured in minutes rather than days, provided you are already running Filament V4.
- Does this package support Filament V3 or only Filament V4?
- It targets Filament V4's Tiptap-based RichEditor and is not a backport to V3, so being on Filament V4 is a hard precondition. The package builds on Filament's asset pipeline and editor internals, which differ from earlier versions. Check the declared Composer constraint against your locked Filament version before merging.
- Is it a Panel plugin, a per-field method, or both?
- The expected integration path is registering it as a plugin in your PanelProvider, with an optional per-field opt-in for scoping it to selected editors. Whether a fluent method such as fullscreen() exists on the field itself is not confirmed in the documentation available. Confirm the exact API surface with the maintainer or the README before committing to an approach.
- Will it conflict with my existing Rich Editor toolbar buttons or Tiptap extensions?
- Toolbar contention is the most likely source of trouble: button ordering, duplicated Tiptap extensions, or Alpine component lifecycle clashes. If your panels already own a customized RichEditor toolbar, inventory those customizations first and reconcile them. Spike the package in a non-production panel so any conflict surfaces before it reaches authors.
- Does enabling fullscreen change how content is saved or stored?
- No. Content written with the plugin enabled is byte-identical to content written without it, because fullscreen only affects the viewport. There is no schema change, no data migration, and nothing new in the serialized output.
- How do I remove the package if we decide not to keep it?
- Removal is composer remove mdobes/rich-editor-fullscreen plus deleting the single entry from your plugins([]) array. The editor degrades gracefully to the stock Filament Rich Editor with no cleanup of stored content required. That reversibility is the strongest argument for trying it rather than building the feature yourself.
- How does it behave with Livewire, wire:navigate, SPA mode, and open Filament modals?
- These are the classic failure points for small editor plugins: focus trapping, ESC handling, body scroll lock, z-index against Filament modals, and state teardown on navigation. Correct behavior with wire:navigate and SPA mode is unverified, as is compatibility with Filament's Vite-based asset publishing under a strict CSP. Test with modals open and after client-side navigation before shipping.
- Is it accessible and does it work well on mobile and in dark mode?
- Accessibility details such as focus trapping, keyboard exit, screen-reader labeling, touch behavior, and dark mode support are open questions rather than documented guarantees. Because the package is small and unvalidated, treat these as items to verify manually in your own panel. Include a keyboard-only and a mobile pass in your spike.
- Is the package mature enough for production use?
- Maturity signals are weak: roughly 9 stars, 0 dependents, a single apparent release, and a composite score around 19.9, so there is no ecosystem validation to borrow confidence from. The MIT license is confirmed, and the blast radius is small and fully reversible. Verify the supported Filament, PHP, Laravel, and Livewire matrix and whether CI tests it, and keep a fork option open given Filament's moving editor APIs.