镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Control layout mode via URL parameter and/or default config #346

Open

Description

@thejjw

Hello,

As a system administrator/user who hosts our own ATT&CK Navigator instance, I’d like to present users an option to generate navigator url to be shared that can set layout options (show id, show name, mini, side, flat layout).

e.g. If a user wants to host iframe with navigator src url that only shows id and not name, they can use src url like:
http://localnavigator/#layerURL=http%3A%2F%2Flocalnavigator%2Flayer.json&showName=false&showID=true
or to use layout like mini:
http://localnavigator/#layerURL=http%3A%2F%2Flocalnavigator%2Flayer.json&layout=mini

I see such variables are already present as properties of viewModel.layout…but I cannot easily find a way to have them embed such properties as url or modify some config switch from host side. Is it somehow possible in current v4.3 navigator?
If not, could you consider adding such features?

Thanks.

Activity

  1. isaisabel commented on Sep 2, 2021

    @isaisabel
    Contributor

    Hi @thejjw,

    This is a really interesting idea and I can definitely see how it would be helpful. It's not possible in the current application unfortunately, but I think we could add it in an upcoming release if we position it as an "override."

    • New layers opened in the application would get that config by default (see also Default technique state #123)
    • Existing layers opened in the application by any means would have their config replaced with any overridden config settings (e.g layout=mini)
    • An additional setting, "allow changes to overridden fields" (default true) would allow the user to disable customization of fields which are overridden. So that way you could set it to the mini layout and disallow users from editing that value (at least not without changing the override settings in the query string).
  2. thejjw commented on Sep 2, 2021

    @thejjw
    Author

    @isaisabel That would fit my need perfectly. Thanks for consideration!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Points: 55 agile story pointsenhancementNew feature or requesttimescale/short-termBecomes timescale/imminent in weeks or months

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions