# Perspective Template Web Nav 8.1 **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [February 24, 2022, 8:07am UTC](https://forum.inductiveautomation.com/t/perspective-template-web-nav-8-1/56497 "2022-02-24T08:07:15Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [February 25, 2022, 4:50pm UTC](https://forum.inductiveautomation.com/t/perspective-template-web-nav-8-1/56497/5 "2022-02-25T16:50:54Z")
Reading back through your second post, I think that you've missed interpreted some things. 1. The only parameters passed to the view are Path, breakpointLarge, and breakpointMedium. 2. The "Header" view's size parameter would have to be set from where it is embedded. It seems like this is bound to the breakpoint container's position.size property which would dictate if the embedded container was in the Large or Small breakpoint. 3. It appears that they are Embedding a breakpoint container in order to get 3 breakpoints, a breakpoint container by itself can only have a small and a large size, but by embedding a breakpoint container you can set it's large size to the same as the small size of the parent and effectively have large, medium, and small containers. 4. As far as I am aware there is no notion of identically named parameters being passed down through many calls. In the example you have shown, the path parameter is sent to the view, inside that view (Framework/Breakpoint) there is undoubtedly an embedded view component which has its path property bound to self.view.params.path. You have to specify the parameters at the Parent level in order for it to be aware of any child level parameters. Here is a decent post that I think may help explain things a little better. > [@Pass Parameter between pages](https://forum.inductiveautomation.com/t/pass-parameter-between-pages/21108/2): > > I’m going to break my answer into two pieces because there’s a lot of confusion around the terminology between Views, Pages, Windows, and Sessions. To be clear, Windows are Vision, so I won’t be tackling that here. The only way to pass values between sessions is either through the database or Tags, so we’ll gloss past that as well. Part One - Passing Values Between Views: To pass a parameter to an Embedded View, create a new EmbeddedView.props.params property for each key you’d like to send. T… --- _[View the full topic](https://forum.inductiveautomation.com/t/perspective-template-web-nav-8-1/56497)._