Fascinating. Curious to learn how you were able to measure this; admittedly when I have hunches like this I just record my screen and then note the time on the video player. Not too scientific so Im hoping to maybe add a new skill to my toolbelt.
Hello guys, “fill” should be working now, can you guys check? @TomCargolo the performance problem should be fixed as well.
There is a major weakness of the new icon system, that it is not possible to dynamically set the icon from supabase/xano or any other external database.
Since weweb sets the icons during the build face, it does not matter what icons you have activated/added - they are simply not there if they are not defined manually.
This is also not properly documented in the documentation, that should be updated.
This was not a weakness with the old icon sets.
To mitigate you have to manually add all icons as a comment in the header, or use them “hardcoded” some other place in your app.
I believe there should a be a less manual way of deciding what icons should be built by your app. Either activating the icons sets or individual icons in the assets icons menu should add them , or by dynamically supply a list over icons you want to be included in the build. If performance or app size if a problem with too many icons added there should be a warning in the icons assets menu when too many are added.
Wewebs own suggestion is adding a comment in the header like this, for information:
<!-- phosphor-regular/basket phosphor-regular/list-dashes phosphor-regular/plus-square -->
i’ve done this and can confirm that this works.
Looks like the fill is working without the CSS workaround! Thanks for fixing this 
1 Like