Weave Code
Popover Laravel Package
lara-zeus/popover
lara-zeus/popover adds a lightweight popover component for Laravel and Filament apps, letting you attach rich HTML or Livewire content to buttons and links with a few lines of Blade. Configure placement, width, and trigger behavior while keeping markup clean, ideal for inline help, quick actions, an...
lara-zeus/popover is a lightweight plugin that brings popover support to your Filament panels, letting you surface rich content in an overlay triggered by hover or click. It integrates cleanly with Filament forms and actions, so you can attach contextual help, extra details, or compact layouts without cluttering the main UI.
- Hover and click triggers
- Works with Filament actions and form components
- Accepts Blade views for custom popover content
- Configurable placement and offset
- Simple, minimal setup
Frequently asked questions about Popover
- What is lara-zeus/popover and what does it actually do?
- Lara Zeus Popover is a presentation-layer component for FilamentPHP panels, not a general Laravel package. It ships PopoverColumn for tables and PopoverEntry for infolists, which render custom content from a closure, usually a Blade partial, into an Alpine-driven overlay. You use it to show rich HTML, tooltips, or contextual details when a user hovers or clicks a table cell or infolist entry. It has no service provider, migrations, or publishable config in the default path, so its architectural footprint is minimal.
- How do I install lara-zeus/popover in a Laravel application?
- Install it with Composer using composer require lara-zeus/popover, then import the PopoverColumn or PopoverEntry classes where you need them. There is no service provider registration, no migrations, and no config file to publish in the standard installation. The first working popover is typically an hours-not-days task: register the column on one read-only table field, write a Blade partial, and hover the cell.
- Which Filament versions does lara-zeus/popover support?
- The package targets Filament v3-era table and infolist conventions, and the component classes extend Filament's own APIs. Because Filament's minor releases move quickly, check which exact Filament minor is pinned in your composer lockfile and confirm the installed tag resolves against it. Treat Filament commitment as a precondition for adopting the package rather than an outcome of it.
- Can I use lara-zeus/popover outside Filament or in a public-facing app?
- No, the package is built for Filament panels and its column and entry classes only make sense inside a Filament table or infolist schema. The content itself is authored in Blade partials, but the components that trigger and position the overlay are Filament-specific. It is also a poor fit for public-facing screens or anywhere the popover would be the primary navigation affordance; it belongs on internal admin surfaces.
- How do I render custom HTML or a Blade view inside a popover?
- You pass a closure to the component's content method and return either a view partial or inline HTML. Prefer view partials unconditionally, because they are easier to review, test, and change without touching table or infolist definitions. A partial also keeps markup out of your schema code and makes the escaping behaviour easier to audit.
- Is lara-zeus/popover safe for user-supplied data, or is there an XSS risk?
- Escaping behaviour is undocumented, so you must inspect the wrapper Blade view before trusting it. If that view raw-emits content with unescaped output, every partial becomes an explicit-escaping obligation and a single missed escape is an XSS path inside a privileged admin panel. Read the source, confirm how the content flows, and avoid feeding user-derived data into a popover until you have verified it.
- Does lara-zeus/popover handle accessibility, keyboard triggers, and mobile touch?
- Accessibility is unverified and unclaimed by the package; there is no stated a11y policy. Keyboard triggering, Escape-to-close, focus management, screen-reader announcement, and touch target sizing are all unproven. That realistically limits it to internal admin screens where a native modal or tooltip fallback is acceptable if the popover proves unusable.
- Do popovers work inside scrollable tables, relation managers, or the last column?
- This is where this class of component typically breaks, because table cells clip overflowing content and the containing block controls positioning. Popovers in scrollable tables, relation managers, and edge columns are the highest-risk placements. Test those cases explicitly in your Filament panel before rolling the component out broadly.
- Who maintains lara-zeus/popover and what are the maintenance risks?
- The package has a single maintainer, around 31 stars, and zero dependents, so there is no downstream canary to warn you when something breaks. Because the components extend Filament table and infolist APIs, a Filament minor bump can break rendering with no upstream notice and no community reports to consult. Recent releases have been documentation and state-resolution fixes rather than new features, so pin the version, read the source, and keep the capacity to fork on hand.
- What are alternatives to lara-zeus/popover in a Filament panel?
- The main alternatives are Filament's built-in tooltip support, a modal action that opens a dedicated view, or a full page for the related record. Native options are safer for accessibility, keyboard handling, and clipping, but they are heavier than a hover popover. Decide your fallback before adopting the package and treat the popover as an additive enhancement only.
Weaver
How can I help you explore Laravel packages today?