Document Handler - Active drawer content bug

[OlofSvahnVbg]

There seems to be a problem with the client reading certain settings. In admin, these settings in "Inställningar"...

do not get set properly in app.js. This is because of logic in the functions isDrawerPermanent, isDrawerVisible and isDrawerStatic. In these functions there is a separate if-statement like this:

    if (drawerProps.activeDrawerContentState === null) {
      return false;
    }

The problem is that when loading the site for the first time (without local storage, or cookies etc...) the activeDrawerContentState is null.

This, in in turn, is because it gets set to null in the constructor here:

    const activeDrawerContentState = canRenderCustomDrawer
      ? activeDrawerContentFromLocalStorage !== null &&
        activeDrawerContentFromLocalStorage !== "plugins"
        ? activeDrawerContentFromLocalStorage
        : this.props.config.mapConfig.map.activeDrawerOnStart
      : canRenderDefaultDrawer
      ? "plugins"
      : null;

BUT! It seems this only happens if the "Aktiv drawer innehåll" is set to "plugins" or nothing (empty):

If the field is set to "documenthandler", the activeDrawerContentState gets set to this.props.config.mapConfig.map.activeDrawerOnStart.

I don't know if this is intentional or something. But it seems a bit strange.
Please comment if you know why this happens, and/or why it happens.

The bug doesn't seem to be browser specific.

[Hallbergs]

Sounds like a bug to me. Not surprised since the logic around the active drawer content is a bit.... intricate.