This article covers what you need to use Bento effectively, as well as common conflicts Bento runs into.
In order to use Bento, you need:
A web application that your users can access using a web browser. Your application must be accessible over the internet by a URL (i.e., connected to a network)
The ability to install a snippet of code into that application
Google chrome or Brave for guide creation. (Don't worry your experiences will be shown on all browsers)
Browser support
Building Bento guides will works across every modern browser experience, but there are some limitations when using our visual builder for placing guides in your app.
The visual builder works best with:
Brave (with shields turned off). Read more here
Google Chrome
You need to download the chrome extension to use the visual no code editor. Download here.
We currently do not support Safari or Firefox. We recommend turning off any ad-blockers for the most seamless experience.
Webpage support
Bento supports the following web applications:
Javascript
Angular
React
Single page apps (SPA's)
Element selection
We support everything your browser does by default. If you have any doubts, this checker will help you validate.
We support shadow DOMs
We "observe" the DOM changes and if there isn't a change we don't preform additional checks for the element to avoid impacting your app speed with infinite loops.
iFrames
Native and 3rd party iFrames need the Bento snippet installed within it
Additional limitations
Bento pop-up components do not work well on applications that use the newer CSS concept of 'Isolation'