FTUI version 3

[mr_petz]

Das @click wird natürlich bei jedem click auf dem button gesendet...
LG

[Wolfgang Hochweller]

Danke. Genau das moechte ich haben.

Da ich mit den Circlemenus nicht wirklich gluecklich war, habe ich sie durch Popups mit Buttons ersetzt.
Und schliesse das Popup, wenn ich irgendeinen der Buttons angeklickt habe, damit ich nicht auf das automatische Close warten muss.

[grossmaggul]

Also entweder ist bei dem letzten Update vor einer Stunde was schief gelaufen oder man muss eine andere Syntax verwenden.
Jedenfalls sehe ich jetzt gar nichts mehr, die Seite ist leer, weder Menü noch Tabs zu sehen.

[OdfFhem]

@grossmaggul

In einem solchen Fall wäre ein Blick in die (hoffentlich zugängliche) "Console" des Browsers hilfreich ... dort werden (normalerweise) u.a. aufgetretene Fehler ausgegeben ...

[MDietrich]

nach dem Update habe ich das gleiche Problem.

Gemäß GOOGLE: 21 errors

Code Auswählen Erweitern


ftui.helper.js:152 Failed to load ../../components/title/title.component.js TypeError: Failed to fetch dynamically imported module: http://xxx.xxx.xxx.xxx:8083/fhem/ftui3/components/title/title.component.js
error @ ftui.helper.js:152
loadModule @ ftui.app.js:107
await in loadModule (async)
(anonymous) @ ftui.app.js:136
loadUndefinedComponents @ ftui.app.js:132
initComponents @ ftui.app.js:95
initContent @ content.component.js:98
loadFileContent @ content.component.js:89
await in loadFileContent (async)
FtuiContent @ content.component.js:26
(anonymous) @ content.component.js:103



Code Auswählen Erweitern


[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89


[setstate]

Hallo zusammen

Kann mir jemand erklären wie ich den Title in examples/menu.html anpassen kann? Color etc?
Welche components ist dafür verantwortlich? view-toolbar.js?
Definieren tue ich den Title in:

Code Auswählen Erweitern

<ftui-tab-view id="View2">
      <ftui-content file="examples/contents/content-view1.html" room="sound"></ftui-content>
    </ftui-tab-view>

Grüsse und danke

EDIT:
gefunden
Uhi.... Vielleicht sollte ich auch mal in die content-view1 schauen 
aber ein linksbündig nimmt er dort leider nicht. Gedankenfehler?

Code Auswählen Erweitern

  <ftui-view-toolbar>
    <ftui-title align-items="left" >{{room}}</ftui-title>
  </ftui-view-toolbar>



Muss das ftui-view-toolbar mir dem title in jede content Seite? Ging das nicht mal über die Index ?

Code Auswählen Erweitern


<ftui-tab view="view2" title="Sound"></ftui-tab>


Die Beispiel habe ich jetzt überarbeitet. Es gibt jetzt beide Möglichkeiten:
1.) einmal ist die Toolbar mit Menü-Button und Titel in jedem View wiederholt mit drin.

https://knowthelist.github.io/ftui/www/ftui/examples/menu.html

  <ftui-main>
    <ftui-tab-view>
        <ftui-view>
             <ftui-view-toolbar>
                 {{beliebigerTextAlsTitle}}


2.) oder, Menü-Button und Titel gibt es nur einmal

https://knowthelist.github.io/ftui/www/ftui/examples/menu2.html oder https://knowthelist.github.io/ftui/www/ftui/examples/mobile.html

  <ftui-main>
    <ftui-view>

      <ftui-view-toolbar slot="header">
        <ftui-menu-button slot="start"></ftui-menu-button>
        <ftui-tab-title text-align="left"></ftui-tab-title>
      </ftui-view-toolbar>

      <ftui-tab-view>

Dann muss man ftui-tab-title  benutzen, um von den aktivierten Tabs den Text zu bekommen.

[setstate]

nach dem Update habe ich das gleiche Problem.

Gemäß GOOGLE: 21 errors

Code Auswählen Erweitern


ftui.helper.js:152 Failed to load ../../components/title/title.component.js TypeError: Failed to fetch dynamically imported module: http://xxx.xxx.xxx.xxx:8083/fhem/ftui3/components/title/title.component.js
error @ ftui.helper.js:152
loadModule @ ftui.app.js:107
await in loadModule (async)
(anonymous) @ ftui.app.js:136
loadUndefinedComponents @ ftui.app.js:132
initComponents @ ftui.app.js:95
initContent @ content.component.js:98
loadFileContent @ content.component.js:89
await in loadFileContent (async)
FtuiContent @ content.component.js:26
(anonymous) @ content.component.js:103



Code Auswählen Erweitern


[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
(anonymous) @ thermostat.component.js:498
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89


Es sieht so aus, als ob in der  thermostat.component.js <ftui-title> benutzt wird. Die gibt es nicht mehr. Müsste durch <ftui-label> ersetzt werden.

[OdfFhem]

thermostat.component.js verwendet scheinbar weder ftui-title noch ftui-label ...

Kann es denn sein, dass die nutzereigene Seite ftui- title verwendet ?

[mr_petz]

Ja ich habe weder <ftui-title> noch <ftui-label>...
"nur" <ftui-icon>. Wird da auch auf title zugegriffen?

Der Fehler sagt ja was von touchmove bei thermostat und bei button von touchstart event listener???

Code Auswählen Erweitern


button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonymous) @ button.component.js:82
thermostat.component.js:38 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiThermostat @ thermostat.component.js:38
initContent @ content.component.js:96
loadFileContent @ content.component.js:89


Edit: kann bei mir ohne content keinen Fehler unter Chrome am thermostat feststellen...

@setstate
sollte man jetzt

Code Auswählen Erweitern


{ passive: true }

oder

Code Auswählen Erweitern


{ passive: !ns.includes('noPreventDefault') }

dem EventListener mitgeben? (bei eigener Komponente)

[MDietrich]

Guten Morgen,
ja, in einem content-file hatte ich ftui-title verwendet und gerade entfernt.

Die Fehlermeldung sieht jetzt so aus:

Code Auswählen Erweitern


Failed to load resource: the server responded with a status of 404 (Not Found)
components/tab/tab-title.component.js:1 Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
5ftui.helper.js:152 Failed to load ../../components/tab/tab.component.js TypeError: Failed to fetch dynamically imported module: http://xxx.xxx.xxx.xxx:8083/fhem/ftui3/components/tab/tab.component.js
error @ ftui.helper.js:152
color-attributes.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
color-attributes.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
color-attributes.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
color-attributes.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
5ftui.helper.js:152 [ftuiApp] error: initComponents - Timed out in 5000ms.

Könnte sich da ein "/" eingeschlichen haben:

Code Auswählen Erweitern

File not found: ./www/ftui//components/tab/tab-title.component.js

EDIT: Die Datei ist nicht vorhanden und wird auch bei einem "update all https://raw.githubusercontent.com/knowthelist/ftui/master/controls_ftui.txt" nicht geladen

EDIT 2: Habe die Datei manuell aus dem git kopiert, habe jetzt neue Meldungen:

Code Auswählen Erweitern

GET http://matthiasdietrich.noip.me:8083/fhem/themes/color-attributes.css net::ERR_ABORTED 404 (Not Found)
was nachvollziehbar ist, das sie Datei ja im FTUI Verzeichnis liegt

Code Auswählen Erweitern

ftui.helper.js:152 Failed to load ../../components/tab/tab.component.js SyntaxError: Unexpected token '<'
error @ ftui.helper.js:152
loadModule @ ftui.app.js:107
await in loadModule (async)
(anonymous) @ ftui.app.js:136
loadUndefinedComponents @ ftui.app.js:132
initComponents @ ftui.app.js:95
initContent @ content.component.js:98
loadFileContent @ content.component.js:89
await in loadFileContent (async)
FtuiContent @ content.component.js:26
(anonymous) @ content.component.js:103




Viele Grüße
MDietrich

[grossmaggul]

In einem solchen Fall wäre ein Blick in die (hoffentlich zugängliche) "Console" des Browsers hilfreich

Bevor ich hier alles mit Konsolenausgaben vollmülle, wollte ich erstmal wissen, ob das Problem mal wieder vor meinem Rechner sitzt.

Aber gut, beim Reload der Seite bekomme ich zig Fehlermeldung mit diesem Wortlaut:

Code Auswählen Erweitern

button.component.js:19 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
FtuiButton @ button.component.js:19
(anonym) @ button.component.js:82


Allerdings nicht nur für "button.component.js" sondern auch für "thermostat.*, knob.* und volume3d.*"

Da kommen aber noch mehr Fehler:

Code Auswählen Erweitern

jquery.flot.js:3151 Uncaught TypeError: Cannot read properties of null (reading 'save')
    at G (jquery.flot.js:3151:18)
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
about:client:1 GET http://192.168.1.12:8083/fhem/themes/color-attributes.css net::ERR_ABORTED 404 (Not Found)
ftui.helper.js:152 Failed to load ../../components/tab/tab.component.js TypeError: Failed to fetch dynamically imported module: http://192.168.1.12:8083/fhem/ftui/components/tab/tab.component.js
error @ ftui.helper.js:152
loadModule @ ftui.app.js:107
await in loadModule (async)
(anonym) @ ftui.app.js:136
loadUndefinedComponents @ ftui.app.js:132
initComponents @ ftui.app.js:95
initPage @ ftui.app.js:79
init @ ftui.app.js:66
await in init (async)
main @ ftui.js:7
await in main (async)
(anonym) @ ftui.js:19
calendar.component.js:138 refresh ftui_calendar_1
chart.component.js:321 Uncaught TypeError: dataElement.fetch is not a function
    at chart.component.js:321:19
    at NodeList.forEach (<anonymous>)
    at FtuiChart.refresh (chart.component.js:315:23)
    at FtuiChart.onAttributeChanged (chart.component.js:301:14)
    at FtuiChart.attributeChangedCallback (element.component.js:76:12)
    at FtuiChart.set (element.component.js:164:25)
    at FtuiChart.onAttributeChanged (chart.component.js:296:21)
    at FtuiChart.attributeChangedCallback (element.component.js:76:12)
    at HTMLElement.initContent (content.component.js:96:20)
    at HTMLElement.loadFileContent (content.component.js:89:10)
(anonym) @ chart.component.js:321
refresh @ chart.component.js:315
onAttributeChanged @ chart.component.js:301
attributeChangedCallback @ element.component.js:76
set @ element.component.js:164
onAttributeChanged @ chart.component.js:296
attributeChangedCallback @ element.component.js:76
initContent @ content.component.js:96
loadFileContent @ content.component.js:89
await in loadFileContent (async)
FtuiContent @ content.component.js:26
(anonym) @ content.component.js:103
7[Violation] 'ftuiDataChanged' handler Zeit: <N> ms


Achso, das passiert übrigens auch, wenn man die mitgelieferte index.html aufruft und die Fehlermeldung dazu:

Code Auswählen Erweitern

[Violation] Added non-passive event listener to a scroll-blocking <some>-Ereignis. Consider marking event handler as 'passive' to make the page more responsive. See <URL>
[Violation] Forced reflow while executing JavaScript took 50ms
tab-title.component.js:1 Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
ftui.helper.js:152 Failed to load ../../components/tab/tab.component.js TypeError: Failed to fetch dynamically imported module: http://192.168.1.12:8083/fhem/ftui/components/tab/tab.component.js
error @ ftui.helper.js:152
loadModule @ ftui.app.js:107
await in loadModule (async)
(anonym) @ ftui.app.js:136
loadUndefinedComponents @ ftui.app.js:132
initComponents @ ftui.app.js:95
initPage @ ftui.app.js:79
init @ ftui.app.js:66
await in init (async)
main @ ftui.js:7
await in main (async)
(anonym) @ ftui.js:19
fhem.service.js:232 connect visible: true
fhem.service.js:131 Fri Jan 14 2022 09:57:00 GMT+0100 (Mitteleuropäische Normalzeit) '[refresh] start now isOffline:' false 'isAppVisible()' true
ftui.helper.js:152 [ftuiApp] error: initComponents - Timed out in 5000ms.
error @ ftui.helper.js:152
(anonym) @ ftui.app.js:97
Promise.catch (async)
initComponents @ ftui.app.js:96
initPage @ ftui.app.js:79
init @ ftui.app.js:66
await in init (async)
main @ ftui.js:7
await in main (async)
(anonym) @ ftui.js:19
fhem.service.js:232 connect visible: true
fhem.service.js:131 Fri Jan 14 2022 09:57:04 GMT+0100 (Mitteleuropäische Normalzeit) '[refresh] start now isOffline:' false 'isAppVisible()' true
fhem.service.js:399 [healthCheck]  Fri Jan 14 2022 09:58:11 GMT+0100 (Mitteleuropäische Normalzeit) 3 isAppVisible(): true

[MDietrich]

Hallo,
ich habe es gerade auch noch einmal mit dem Laden der Original index.html versucht.
Auch hier bleibt der Bildschirm mit Ausnahme eines grid-tiles leer.

Fehlermeldungen:

Code Auswählen Erweitern


ftui.helper.js:152 Failed to load ../../components/tab/tab.component.js SyntaxError: Unexpected token '<'
error @ ftui.helper.js:152
ftui.helper.js:152 [ftuiApp] error: initComponents - Timed out in 5000ms.
error @ ftui.helper.js:152
(anonymous) @ ftui.app.js:97

Es wäre toll, wenn es bald wieder vorwärts ginge. Wenn ich helfen kann, dann bitte melden!

Gruß,
MDietrich

[mr_petz]

In der Online Demo index.html geht es aber...
https://knowthelist.github.io/ftui/www/ftui/index.html

cache leeren???

LG mr_petz

[MDietrich]

Hallo mr_petz,

ja, wenn ich die Datei im git öffne funktioniert es.

Auf meinem pi habe ich gerade die Dateien im Ordner ..\components\tab sowie die index.html gelöscht,
und mit "update all https://raw.githubusercontent.com/knowthelist/ftui/master/controls_ftui.txt" neu installiert.
Die Datei tab-title.components wird dabei wieder nicht geladen. Es händisch kopiert, jetzt funktioniert es wieder.

ftui-label war nicht die Ursache, hier wird jetzt einfach Nichts angezeigt.

Danke Allen für die Unterstüzung.

Auf zur nächsten Herausforderung grid im grid (via content mit mehrfachem Aufruf)
Gruß,
MDietrich

[grossmaggul]

Ah, danke, es reicht aber einfach die tab-title.components herunterzuladen und ins component/tab Verzeichnis zu legen.