Arvados

Another use case similar to this would be to permanently display a disclaimer on specific environments. E.g. some users are not able to distinguish between our dev/test environment and upload production data. The banner could inform them permanently that this is a dev/test environment.

18368-workbench-banner-config @ 3a21e39416ea3fadc795f52b77e68b36d55436ed

• Add Workbench.BannerURL config option

developer-run-tests: #3315

18368-workbench-banner-config LGTM, thanks.

Danny will add a screenshot, need to iterate on the design.

Add an explicit close button [x]

slight transparency: 90% or 80% opacity

Different background color.

Consider using dialog box control, or integrating better into layout so it doesn't cover anything up.

From discussion with Moritz:

• For now, use the plain dialog box control for the overlay.
• Load HTML from the config URL and injects it as raw HTML into the content of the box (it is the responsibility of the user for it to be well formed, we're assuming only admins are allowed to set the contents.)
• When dialog box is dismissed, record in local storage that the dialog box was displayed.
  • It should record the URL, the date, and the ETag from the request headers
  • On reloading the app: If the local storage says the dialog box was previously shown, check the URL and headers in local storage. If the URL, date or ETag has changed, redisplay the dialog. If not, suppress it.
• There should be a menu item (perhaps under the bell "notify" menu) which redisplays the dialog.