Dev-mode guard for the tab chrome's one genuine failure mode: the .mj-tabs* styles live in a
GLOBAL stylesheet (@memberjunction/ng-ui-components/dist/lib/tabs/tabs.scss), and a standalone
host that forgets the import gets structurally-working but completely unstyled strips — bare divs,
silently, with no error anywhere. This turns that silence into an actionable console warning.
Detection: tabs.scss sets --mj-tabs-chrome-loaded: 1 on .mj-tabs. If the computed value is
absent on a rendered strip, the sheet isn't in the page. Dev-mode only, once per app, and never
throws — a missing stylesheet must not take the component down with it.
Called by BOTH strips (mj-tabstrip and mj-workspace-tab-strip) after view init.
Dev-mode guard for the tab chrome's one genuine failure mode: the
.mj-tabs*styles live in a GLOBAL stylesheet (@memberjunction/ng-ui-components/dist/lib/tabs/tabs.scss), and a standalone host that forgets the import gets structurally-working but completely unstyled strips — bare divs, silently, with no error anywhere. This turns that silence into an actionable console warning.Detection:
tabs.scsssets--mj-tabs-chrome-loaded: 1on.mj-tabs. If the computed value is absent on a rendered strip, the sheet isn't in the page. Dev-mode only, once per app, and never throws — a missing stylesheet must not take the component down with it.Called by BOTH strips (
mj-tabstripandmj-workspace-tab-strip) after view init.