From: <ga...@cu...> - 2015-04-11 08:09:16
|
Hi, About the navbar scrolling behavior for the project sites, I see it's been implemented for the fixed top page header, which works smoothly. IIRC, luci's description last fall was that the topbar would afix to the viewport top when the page is scrolled. I'm thinking maybe that second effect maybe isn't such a good idea. I implemented that also in my localhost branch 14 and it works ok, but isn't ideal. One problem is that at other examples I see, the navbar that rises and sticks to the top is an element that's at the same DOM level as the page header and middle (or main content div). Tiki's HTML isn't set up that way currently that at least in fivealive-lite there's a visual problem because the full-width middle, which has the background "border" at its top scrolls up along with the page content, and the topbar module zone sticks at the viewport as it should, but it loses its background, which scrolled up out of sight. I added a topbar background so the links do have a background, but this is is just the topbar (i.e., container) width. Actually in my test it's container width on the left but goes off the screen on the right, but I don't know if this is just due to an implementation detail. This is all with the "fixed_top_modules" layout template, which I tested with because otherwise it's pretty solid. Anyway, visual glitches aside, I'm finding the UI is kind of sketchy with this arrangement. It's easy to to miss the narrow affixed top bar with the pointer and hit the page header bottom margin instead, which brings down the page header and covers the aimed-for link. And the movement of the two scrolling sections, while fluid and so on, gives a not-so-solid impression about navigation, somehow IMO. If the user spends more time messing with page scrolling to position links to click, it kind of defeats the purpose of improving UI with the affixed topbar. Maybe if luci is working on implementing the affixed topbar he's getting better results, which would be great, but I think the touchiness involved with the narrow link area (the topbar) would be the same problem in any implementation. So bottom line is maybe the scrolling that's currently set up the project sites is enough, and no need for the affixed topbar. -- Gary |