[sandbox] Add Hero_browser to hero sandbox to work with slices #279

Open
opened 2026-06-11 11:26:57 +00:00 by mik-tf · 2 comments
Owner
No description provided.
mik-tf changed title from Add Hero_browser to hero sandbox to work with slices to [sandbox] Add Hero_browser to hero sandbox to work with slices 2026-06-14 04:32:22 +00:00
mik-tf self-assigned this 2026-06-14 04:32:23 +00:00
Author
Owner

This one has an empty description. Could you add a one line restatement of what adding hero_browser for testers should do, for example which app uses it and what a tester should be able to do, so it can be scoped.

Signed-by: mik-tf mik-tf@noreply.invalid

This one has an empty description. Could you add a one line restatement of what adding hero_browser for testers should do, for example which app uses it and what a tester should be able to do, so it can be scoped. Signed-by: mik-tf <mik-tf@noreply.invalid>
Author
Owner

Scoped: hero_browser is the headless Chrome that Slides uses to render its PDF and PowerPoint exports. A member who turns on Slides needs it on the same machine (Slides talks to it locally on a fixed port), so it installs as a per-member service rather than a shared engine. It is now an opt-in app in the install catalog and is pulled in automatically whenever Slides is enabled, and the member setup installs Google Chrome alongside it so exports work out of the box. Shipped to the integration channel and live on the admin instance; verified end to end on a member (launch a browser, render a page, produce a PDF).

Signed-by: mik-tf mik-tf@noreply.invalid

Scoped: hero_browser is the headless Chrome that Slides uses to render its PDF and PowerPoint exports. A member who turns on Slides needs it on the same machine (Slides talks to it locally on a fixed port), so it installs as a per-member service rather than a shared engine. It is now an opt-in app in the install catalog and is pulled in automatically whenever Slides is enabled, and the member setup installs Google Chrome alongside it so exports work out of the box. Shipped to the integration channel and live on the admin instance; verified end to end on a member (launch a browser, render a page, produce a PDF). Signed-by: mik-tf <mik-tf@noreply.invalid>
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/home_lhumina#279
No description provided.