[Improvement] Sync custom logo with browser tab (favicon) & allow CLI override for Custom Title

[Berg-Ziege]

1. Custom logo not reflected in browser tab (favicon)

Currently, the custom logo defined in the dashboard config (branding.logo) is only used inside the dashboard UI.
The browser tab icon (favicon) still shows the default Robot Framework logo.

Expected behavior:

• The custom logo should also be embedded into the generated HTML (favicon)
• This ensures consistent branding (UI + browser tab)
• Especially relevant when the logo is already available during dashboard generation (via JSON config)

Additional requirement:

• The provided logo (PNG, arbitrary size/aspect ratio) should be converted to a 48x48 favicon
• It likely makes sense to require or recommend square images to avoid distortion
• If not square, the image should be resized and centered (with padding if needed)

Notes

• Likely requires injecting the favicon into the HTML at build time
• Changing the logo dynamically in the UI is probably not sufficient, since the HTML itself is not updated (only cached assets)

2. CLI argument to override dashboard title (instead of JSON only)

Currently:

The dashboard title in the top bar is defined via JSON:

"branding": {
  "title": "Test 1234"
}

The CLI argument -t / --dashboardtitle sets the HTML<title>(tab name), but not the UI title (Custom Title)

Problem:

• Title is split between:
• HTML title (CLI)
• UI title (JSON)
• This leads to duplication and inconsistent configuration

Expected behavior:

Two possible approaches:

1) Extend -t / --dashboardtitle so it sets:

• HTML title (existing behavior)
• AND the UI title (currently from JSON)

2) Introduce a separate CLI argument (e.g. --dashboard-custom-title) to override only the UI title

Optional behavior:

• CLI argument should override JSON if provided
• Otherwise fallback to JSON config

Use case:

• Title is often determined at runtime (CI/CD, generated dashboards)
• Avoids modifying JSON just to change the title

[timdegroot1996]

@Berg-Ziege sounds like a reasonable improvement. I think I might remove the --dashboardtitle completely and just handle everything in the dashboard/jsonconfig. That makes it a bit easier to find since everything is in 1 place.

The favicon/tab title can then also be set there!

[Berg-Ziege]

@timdegroot1996 Thanks for the feedback!

For my use case, having everything only in the JSON would actually make things more difficult.

The dashboard is generated dynamically, and the title depends on the context (e.g. project / suite name).
Because of that, modifying the JSON for each run is not practical.

The current --dashboardtitle already goes in the right direction, but it would be ideal if:
• it also overrides the UI title (not just the HTML title), or
• an additional CLI argument is introduced for the custom title

So from my perspective, keeping (or extending) CLI-based configuration would be important for dynamic use cases.

Curious what you think about supporting both approaches (JSON as default + CLI override).

[timdegroot1996]

@Berg-Ziege I understand your usecase and I'll think about what makes the most sense. Keeping both with overrides is surely possible but I don't want to make it confusing for users. So I'll let you know what I decide (when I decidee 😄).