Add additional test for app chrome hidden versus chrome visibility

src/core/public/chrome/chrome_service.test.ts

@@ -230,6 +230,28 @@ describe('start', () => {
         ]
       `);
     });
+
+    it('changing visibility has no effect on chrome-hiding application', async () => {
+      const startDeps = defaultStartDeps([new FakeApp('alpha', true)]);
+      const { currentAppId$ } = startDeps.application;
+      const { chrome, service } = await start({ startDeps });
+      const promise = chrome
+        .getIsVisible$()
+        .pipe(toArray())
+        .toPromise();
+
+      currentAppId$.next('alpha');
+      chrome.setIsVisible(true);
+      service.stop();
+
+      await expect(promise).resolves.toMatchInlineSnapshot(`
+        Array [
+          true,
+          false,
+          false,
+        ]
+      `);
+    });
   });
 
   describe('is collapsed', () => {

src/core/public/chrome/chrome_service.tsx

@@ -96,7 +96,7 @@ export class ChromeService {
   }: StartDeps): Promise<InternalChromeStart> {
     /**
      * These observables allow consumers to toggle the chrome visibility via either:
-     *   1. Using setIsVisible() to trigger the next hide$
+     *   1. Using setIsVisible() to trigger the next chromeHidden$
      *   2. Setting `chromeHidden` when registering an application, which will
      *      reset the visibility whenever the next application is mounted
      *   3. Having embed=true in the query string