- How do I install and register filament-quill in a Laravel Filament panel?
- Install it with composer require rawilk/filament-quill, then register the package plugin on the target Filament panel provider. Publish the config and front-end assets as documented, run the Filament asset publish or build step for your panel, and add the field to a form schema. Most of the real effort is verifying that the stylesheet is served and the editor state binds correctly in your panel.
- Which Filament, Laravel, and PHP versions does filament-quill v2 support?
- The v2 line is a major release and appears to track a Filament major, so confirm the official Filament, Laravel, and PHP support matrix in the release notes before pinning. Read the 1.x to 2.x upgrade notes if you have existing installs, and plan to republish or rebuild front-end assets after the major bump. The 2.0.1 patch itself is narrow, but the 2.x version floor is what matters for compatibility.
- Is filament-quill safe for rendering user-submitted HTML, or do I need to sanitize it?
- No. The field produces HTML strings; it does not guarantee safe storage or safe rendering. Sanitize HTML on save or render with a robust sanitizer, and never output stored content unescaped in Blade. Any rich text editor creates an XSS surface if the rendering layer trusts the markup.
- How do I customize the Quill toolbar in filament-quill?
- The package exposes configurable toolbars, so start by publishing the package config and editing the toolbar definition there. If your panel uses a custom Filament theme, verify the published stylesheet and asset build still load the editor correctly. Keep toolbar changes in config rather than patching vendor files so upgrades remain predictable.
- Why did my editor's minimum height change after upgrading to filament-quill v2.0.1?
- In v2.0.1 the editor's minimum height moved from Tailwind @apply utilities to direct CSS, which fixes cases where a purged or custom Tailwind build dropped the height rule. The tradeoff is that older utility-class overrides may no longer apply, and hand-written CSS can collide with panel theme overrides. Move custom sizing into package config or a published stylesheet and verify specificity per panel.
- Why did Shift+Enter behavior change in filament-quill v2.0.1?
- v2.0.1 changed Shift+Enter to produce a soft line break rather than a new paragraph, which is normal rich text editor behavior. Content authored before the fix may render with different paragraph spacing, and downstream parsers, diff tools, or word-count logic that assumed one block per line can see different markup. Test a few existing records after upgrading before assuming rendering is unchanged.
- Does filament-quill work correctly with Livewire re-renders and disabled or read-only fields?
- The client side is a Livewire-aware Alpine wrapper around Quill, so it is designed to work inside Filament forms, but re-renders and disabled or read-only states are exactly what you should verify in your own panel. Confirm editor state stays in sync after Livewire updates and that disabled fields do not allow editing. Check the package tests or add a focused browser test for those flows.
- Does filament-quill support image or file uploads inside the editor?
- This assessment does not establish native image or file upload support, so treat it as something to verify in the README and config before promising it. If uploads are supported, confirm where files are stored, what validation runs, and who can access them. For many teams, pairing the editor with a separate, validated upload field is the safer design.
- Can I use filament-quill with a strict Content Security Policy?
- It depends on whether Quill and the package assets are bundled locally or loaded from a CDN, and whether the integration relies on inline styles or scripts. A strict CSP without unsafe-inline can block editor behavior or styling, so test the actual asset pipeline in a CSP-enabled environment. If needed, self-host assets and adjust the policy rather than weakening CSP globally.
- Is filament-quill actively maintained, and what are the main risks of using it?
- The package is a single-maintainer adapter with an upstream Quill dependency, so bus factor and upgrade latency are the standing risks rather than any one patch. It is a reasonable fit if you are standardized on Filament and can absorb a small presentation-layer dependency. Pin versions, review release notes on major bumps, and keep HTML sanitization in your own application layer.