I wish on this HOME page http://soulskydesign.com/RALE%20Engineering/Predlog_dizajna/index-2.php to hide slide controls (1,2,3,4...) when I moving down. How can I do it?
When I moving down now I can see slider controls behind main menu.
Sorry I miss read your question before. This is easily achievable using
z-index
The z-index property specifies the stack order of an element.
An element with greater stack order is always in front of an element with a lower stack order.
Note: z-index only works on positioned elements (position:absolute, position:relative, or position:fixed).
http://www.w3schools.com/cssref/pr_pos_z-index.asp
What you want to do is put your navigation bar that has your menu to a higher z-index so nothing will be shown in front because other elements have a lower z-index. z-index:99999 would fix your issue.
Related
I'm using v-expansion-panels from Vue, and I notice an odd behaviour: When expanding the panels the page scrolls randomly, sometimes it scrolls leaving the header on the top page, sometimes it scroll way down moving the desired panel out of sight so I have to scroll up.
Is this normal? Is there a way to control this random scrolling, so when expanding the panel the automatic scroll moves the page to the top of the window browser?
Thanks
Gerardo
I tried already all the v-expansion-panels attributes.
I've been trying to implement a rather common UI pattern. I've got a react-navigation MaterialTopTabNavigator that contains a number of ListViews. When the currently active ListView is scrolled down, the header above the Tabs is supposed to be hidden (by translating it up, out of the viewport), the tabs should as well move up.
Like in this picture
The problem I'm facing here is either
a) if i translate the header and the tabs up, i need a paddingTop in the lists to make sure the first item is completely visible. But if i scroll down and the header is hidden and then switch to the next tab (where the list is scrolled to the top) the padding will be visible.
or
b) If i translate the whole thing (header, tabbar, and ListView) the paddingTop is not necessary (I can add a padding at the bottom and hide it via a BottomTabNavigator) but the animation gets jerky on android.
There seems to be a bug in react-native causing this.
But there are apps around for Android that implement this pattern.
I'd be grateful for any ideas or pointers around this.
I have a relative div above a fixed one which acts like a navigation bar.
I want to be able to scroll past the relative div before the fixed div starts having to scroll here is my website.
as you can see from just scrolling on the site the sidebar doesn't work as intended.
Try using JavaScript to detect the scroll position of the window and then change the CSS to start scrolling like a fixed div.
Another tip, the the fixed div which contains your projects on the home page lays over your footer when you scroll to the bottom.
Use JavaScript to detect if the user is at the bottom of the page or not and then set the CSS of it to have a margin from the bottom of the page.
Hope I helped.
I am developing a windows 8 app using JavaScript & HTML.
I have a page which has different sections laid horizontally. I have links for these sections in another page. I want the page to load from that specific section (meaning page should start from this section).
I am using a grid template and have a listview in the main page. When i click on any item in a group ,navigate to that page and come back to the main page. I want the main screen to load from the section that i have selected before.The screen should automatically scroll to that section like how it is happening from semantic zoom.
Any help in this regard will be of great use.
Thanks
For the first part, it should be enough to set the scrollLeft property of the container to the offsetLeft property of the element you want to scroll to.
The second part can be achieved by storing the scrollPosition attribute of the ListView before navigating away and setting it to its old value after navigating back.
As Ma_li said, scroll-left is one solution -- especially for non ListView content. The key here is how much of the experience you want to maintain when navigating back. One option (again, for non-listview content) is to find the element you want to be onscreen, and calling scrollIntoView on the element. However, this only brings the item on screen -- it won't bring it all the way to the left (or right, for BIDI languages), it scrolls just enough to et the whole element on screen.
For ListViews, you should use the indexOfFirstVisibleItem (or, indexOfLastVisibleItem) to scroll the listview to the correct location. This is key, because the listview is a virtualized control, this provides the most accurate & reliable method for scrolling the listview position.
Thanks Dominic & ma_il
I tried document.getElementBy("Id").focus() for the 1st Question and it worked. But i am getting a problem in this.
I have four divs Horizontally say "divA divB divC divD"
Data for the divA is coming from cloud. When i click on the link for divD in the main screen. it is not taking me to the corresponding section for the first time as it takes some time to load the divA. when click on the link for divD second time, it takes to the respective section. It is working if i use setInterval() but the DivA is shown for few seconds when the page loads and then scrolls to divD which is not good.
On Webkit re-rendering any of an outer containers (div in my case) child elements or changing on of these childs display attribute from/to display:none/block/inline/inline-block whatsoever, courses the container element to scroll back to top. This way elements located at the lower end of the scrolling area are never be reached by the user since this area keeps scrolling back to top as soon as one of previously mentioned things occure.
On Firefox the scroll position is maintained as required.
Example (expand left-hand list to force scrollbar to appear or choose an album on the left so that the main display area has enough content to bring up scrollbars, scroll to the bottom and hover over the images)
Is there any workaround/fix I could implement to keep the user experience also for webkit browsers?
Thanks