experiments in a post-browser web
fix(startup): respect startupFeature pref instead of always opening settings
The startup code was hardcoded to always open the settings window,
ignoring the user's startupFeature preference. Now checks the pref
and opens the configured URL (e.g., groups home) or falls back to
settings if not set.
+16
-3
+16
-3
app/index.js
+16
-3
app/index.js
···
509
509
}
510
510
});
511
511
512
-
// Always open settings window on startup
512
+
// Open startup feature (settings by default, or user-configured feature)
513
513
try {
514
-
await openSettingsWindow(p);
514
+
const startupUrl = p.startupFeature || settingsAddress;
515
+
log('core', 'Opening startup feature:', startupUrl);
516
+
517
+
if (startupUrl === settingsAddress) {
518
+
await openSettingsWindow(p);
519
+
} else {
520
+
// Open the configured startup feature
521
+
await windowManager.createWindow(startupUrl, {
522
+
key: startupUrl,
523
+
transparent: true,
524
+
height: p.height || 600,
525
+
width: p.width || 800
526
+
});
527
+
}
515
528
} catch (error) {
516
-
log.error('core', 'Error opening startup settings window:', error);
529
+
log.error('core', 'Error opening startup feature:', error);
517
530
}
518
531
519
532
// Feature enable/disable handler