Error in site navigation

Goodevening,
Please help me to find solutions to my problems,

  1. I created a website but when I click on the links(navbars), for example “заполните бриф” it takes me beyond the boundary( which is denoted by the dotted lines). This is how it looks like, as shown in the picture below.

    This picture below shows how I want the page to look like after clicking the link(navbar), the boundary denoted by the dotted lines should be visible as shown.

This is my website.
http://vyacheslav.webflow.io

Your kind and quick response will greatly be appreciated.

Your’s sincerely Vyacheslav.

Hello @Vyacheslav, could you please reply with a preview link for your website? :smiley:

I think that I could be more helpful if you shared a preview link. Thanks! :wink:

My preview link :smile:
https://preview.webflow.com/preview/vyacheslav?preview=dac8fe076e0e45b83ecf9b9cb5fd1526

Thank you, but it is displaying “404 page not found.” :confused:

https://preview.webflow.com/preview/vyacheslav?preview=cd5aac0fe2be9be2b4ad67456c54c8df

I believe that if you select the “dotted line” element and set it’s opacity to 0% it should work. Instead of setting the “Brif” section to brif, give the dotted line that name under Settings. :smiley:

Try giving your Header Section an ID of home. Since I can’t refresh to view changes in preview mode, I can’t tell if any of this is working haha.

I also recommend heading over to your Style Manager section and click on Clean Up because you have 13 unused classes. :wink:

Thank you . I think this is due to the fact that I was not properly fixed Navbar, tell me how to do it ? For example : http://mansardnye-okna-velux.ru/

Sorry, @MinewireNetwork, but I don’t think changing image opacity will help in this case. Plus if he will put ID “brif” to that image, scrolling will go even further.

What I would recommend is add a bit more padding to section “Brif” (70px instead 30px).

Of course! Click on a Navigation Link and then click on Settings on your Right Panel. Find “Link Settings” then click on “A Section on this Page” and select the corresponding section. :smiley:

Also @sabanna, I thought that he wanted it to go to that image when a certain nav link was clicked but he didn’t want it to be visible.

look 2nd picture: [quote=“Vyacheslav, post:1, topic:18363”]
This picture below shows how I want the page to look like after clicking the link(navbar), the boundary denoted by the dotted lines should be visible as shown.
[/quote]

should be visible :wink:

1 Like

I have done as you wrote , but the problem is that when I turn on the link that I have not seen this line

What exactly do you mean by turning on the link?

I do not speak in English , it is difficult to explain the problem , I’m sorry .
I want to push , and with reference to me appears the line, but when I click on the link I have it goes under the navigation bar

Можешь объяснить на русском, я переведу

Мне нужно зафиксировать навбар в верху страницы, я его зафиксировал, но теперь когда я нажимаю на ссылки в нем у меня переходит на нужную секцию но часть этой секции находится под навбаром. Я хочу сделать так чтобы этого небыло, и секция открывалась полностью

1 Like

Well, so my guess was correct. Vyacheslav wants that picture with dotted line was visible when navigation scrolling site to that section.

So here is something that you should understand. Scrolling navigation moving section to the screen view and stop section when top line of the section touching top line of the browser. In your situation you have 2 ways:

  • add more top padding to the section,
  • add some empty section right before “Brief” and make menu-link pointed to that empty section

P.S. Let me know if you need translation

2 Likes

Извините, что я не мог ! Я не уверен, что то, что сказал sabanna , но я предполагаю, что она помогла вам.

Удачного дня!

2 Likes

I still don’t know what can cause site moving down on load. Have any ideas?

looks like that issue is gone now

I have never experienced that issue before. I hope a staff member can help out, because this might be a bug. :confused: