Trigger Side Menu with toggleNavUi() function | Community
Skip to main content
B
Benoit-Leray
Level 2
April 3, 2016
Solved

Trigger Side Menu with toggleNavUi() function

  • April 3, 2016
  • 2 replies
  • 2342 views

Hi,

looking at benefit from the HTML Gesture API, I'm wondering if there is any parameter to pass to the toggleNavUi() function in order to display not only the Top Nav menu, but the side  menu.

What I'm trying to achieve, is having a hamburger icon straight into my article, than onClick event can display the side menu.

Until now, I reproduce this behavior by having some extra function that display a side menu right inside the article. But I don't like this approach, as it add additional js layer to maintain inside the article.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by nathanm206

    Hi Benoit, there isn't any such parameter in the gesture API, your current approach with your own custom menu is the only workaround. Have you considered making the JS layer global so that it's maintained as a single element shared across multiple articles? That requires using the API to upload shared resources, but it may reduce some of your overhead.

    2 replies

    N
    Adobe Employee
    nathanm206Adobe EmployeeAccepted solution
    Adobe Employee
    April 4, 2016

    Hi Benoit, there isn't any such parameter in the gesture API, your current approach with your own custom menu is the only workaround. Have you considered making the JS layer global so that it's maintained as a single element shared across multiple articles? That requires using the API to upload shared resources, but it may reduce some of your overhead.

      B
      Benoit-LerayAuthor
      Level 2
      April 5, 2016

      Thanks Nathan.

      So you confirm my assumption. I'm already using the shared content with the API to share my .js files.

      I learn in the documentation, that when using shared content, viewer will have to download the whole shared entity before displaying content.

      My preview app still pretty small and light, but final content might become huge to download if all articles are part of the same shared entity.

      Or maybe I missed a point in this shared entity approach.

      Can an article refering to several shared entity? How to achieve that?

      Terms & ConditionsAccessibility statement

      Loading footer...