Limitations of Fibr Editor
Fibr Editor is powerful, but it has boundaries. Understanding these limitations upfront helps you plan better and avoid frustration. For most cases, there's a workaround or alternative approach.
Browser Limitations
Chrome only Fibr Editor runs as a Chrome extension. It doesn't work in Firefox, Safari, Edge, or other browsers. Make sure your team uses Chrome when creating or editing variants.
Extension must be active The editor only works when the Chrome extension is installed and you're signed in. If you're having issues, check that the extension is enabled and you're logged into the correct workspace.
Element Limitations
Some elements can't be edited Fibr works with standard HTML elements, but certain elements may not be editable:
Elements loaded dynamically via JavaScript after page load
Content inside iframes (like embedded videos or third-party widgets)
Elements with heavy JavaScript manipulation (e.g., some React or Vue components)
Canvas elements and WebGL content
Content generated by third-party scripts
Workaround: For elements Fibr can't select, use the HTML edit feature to target them directly, or work with your development team to make those elements accessible.
Complex single-page applications (SPAs) Websites built entirely with React, Angular, or Vue may have limited compatibility. Fibr works best when the DOM structure is stable. If your site heavily manipulates the DOM after load, some edits may not persist correctly.
Workaround: Test thoroughly in preview mode. For SPA-heavy sites, consider having developers expose stable container elements that Fibr can target reliably.
Styling Limitations
Inherited styles may override changes If your site uses CSS with high specificity or !important declarations, Fibr's style changes might not take effect. The editor applies inline styles, which can be overridden by aggressive CSS rules.
Workaround: Use HTML edit mode to add inline styles with !important, or work with your development team to reduce CSS specificity on elements you want to personalize.
Custom fonts require availability You can change font families, but the font must be already loaded on your page or available as a web-safe font. Fibr doesn't upload or host custom fonts.
Workaround: Ask your development team to load any additional fonts you need in the site's CSS, then reference them in Fibr.
Functional Limitations
No backend changes Fibr modifies the front-end presentation layer only. It cannot:
Change server-side logic or API responses
Modify database content
Alter form submission destinations
Affect authentication or user sessions
Workaround: For backend-dependent personalization, work with your development team to create front-end hooks that Fibr can trigger.
No cross-page persistence Edits apply to individual pages. If you change a header on Page A, it won't automatically change on Page B, even if they share the same template.
Workaround: Use Fibr's bulk editing feature to apply similar changes across multiple pages efficiently.
Limited form modification You can edit form labels, placeholder text, and styling. However, you cannot:
Add new form fields that submit data
Change where form data is sent
Modify form validation logic
Workaround: Use widgets to add supplementary lead capture forms that integrate with Fibr's tracking.
Performance Considerations
Very large pages may slow the editor Pages with thousands of DOM elements or heavy media content can make the editor less responsive. The live page won't be affected, but editing may feel sluggish.
Workaround: Close unnecessary browser tabs, or edit on a simplified staging version of the page first.
Multiple conflicting tools If you're running other visual editing tools, heatmapping scripts, or optimization platforms simultaneously, they may conflict with Fibr.
Workaround: Disable other visual editing tools while using Fibr Editor. They can run alongside Fibr in production without issues; conflicts mainly occur during editing.
What Fibr Editor is NOT For
Building pages from scratch
Fibr edits existing pages
Use Fibr Genesis to create new landing pages
Major site redesigns
Too many interdependent changes
Work with developers for structural changes
E-commerce product data
Product info comes from backend
Use your e-commerce platform's tools
Dynamic user-specific content
Requires backend personalization
Integrate with your CDP for data-driven personalization
When to Involve Developers
Fibr Editor handles most marketing-driven changes independently. But some scenarios benefit from developer support:
Making elements "Fibr-friendly" for easier targeting
Loading additional fonts or assets you want to use
Creating stable container elements in SPAs
Setting up backend integrations for advanced personalization
Resolving CSS specificity conflicts
A small amount of developer time upfront can significantly expand what you can do with Fibr independently.
Getting Help
Running into a limitation not covered here? Reach out to [email protected]. We can help you:
Determine if a workaround exists
Suggest alternative approaches
Identify if a feature request makes sense
Last updated