Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Recommended Posts

Posted

Message to @m.roszak.

SVG graphics in QuickApp interface makes it possible to create UI that are more visually attractive than those built only with the standard UI elements or simple HTML.

At the moment, however, SVG is displayed only as an image, so individual parts of the graphic cannot respond to clicks. This is really unfortunate.

 

Even very limited click support would make it possible to create room plans, control panels or installation diagrams even much attractive - because of reaction on a click over the element...

 

I am not suggesting that arbitrary JavaScript should be allowed inside SVG files. That could obviously create security concerns.

However, the controller already supports calling device actions through the existing callAction endpoint, including over HTTPS, like this:

Please login or register to see this code.

 

Perhaps SVG could therefore be given one simple and controlled mechanism that would call such an action when clicked, using the user’s current authenticated session.

For example, it could look like this:

Please login or register to see this code.

 

Such a link would not open a website. Instead, the HC3 interface would intercept it and execute the normal device action call over HTTPS.

This way, the SVG would not need to contain a username, password, or any JavaScript code. Scripts, external links, and other potentially unsafe elements could remain blocked.

Another possible approach could be a dedicated attribute - as an information to the interface what action should be executed.

 

Of course, I do not know how the current interface is implemented or how much work such a change would require. From the user’s point of view, however, even this simple ability to call an existing device function would be enough.

Would it be possible to consider adding this kind of limited click support for SVG?

If anyone agrees with this suggestion, please add your support. Perhaps it will help strengthen our voice.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...