Discussions

Hi,
We are currently developing a plugin that can place videos on the page. Now we ran into the problem that the fullscreen mode does not work. If I am not mistaken, the plugin iframe does not allow it. 
So I wonder if there is any chance that you can add that attribute to the plugin iframe as you have for common widget iframes?

Hi everyone,

Hi everyone,
I am developing an new plugin and want to use the title button in the widget menu. When I insert my plugin and want to set the title, the button does not exist. Do you know how I can enable or display it?
In the documentation I only read that you can change the name of some widgets but not what qualifies it for a widget. And in the documentation I read, that the button is labeled with an 'A', but on my Haiilo page the title buttons are labeled with 'T' for some other widgets.
Best wishes!

If you embed a widget on a "homepage" or in a "content" app, a blue button appears in the mobile app with the text "Show dynamic content". If you embed the same widget in a wiki app or a blog app, the widget is rendered and loaded directly.

Is it possible to customize the error message if for example the input of a text configuration field does not match the pattern?

Hi there,
we are currently developing a plugin which has a custom config view. The Problem is that regardless of the heigt of the content of the iframe, there is always a scroll bar, which makes it look a bit ugly. We found that the iframe element insidie of the coyo-iframe component has the css property "display: inline" which is the standard behaviour of an iframe. However this causes the scrollbar to always appear. Is there any way, we could set the iframe to a block element (display: "block"). This would solve the scrollbar problem, at least for this specific use case.

Hey team,

I am using the "observeHeight" function provided by the plugin adapter. And have noticed the following:

Hey,

Hi there :)
I am using Quasar with webpack for the frontend of my Plugin. I updated to the newest Version of the Plugin Adapter ( 1.1.0 ) and it broke the build of the frontend because of the static keyword from your plugin. This is used at 2 locations in the Plugin adapter: