Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

Re: Major update to

by DStaal (Chaplain)
on Jul 17, 2009 at 17:42 UTC ( #781123=note: print w/replies, xml ) Need Help??

in reply to Major update to

I do wish there was a way to turn off the 'floating' top bar: I'm sure it's nice for most, but it completely kills my work desktop. (Ok, so a lot of things kill this desktop, but not being able to scroll through documentation is going to annoy me.)

Replies are listed 'Best First'.
Re^2: Major update to
by LanX (Sage) on Jul 18, 2009 at 04:47 UTC
    It's also slowing down scrolling ("unsmoothing", kind of stumbling) ... I'd really love to have a setting stored in the cookie to disable/manipulate the floating bar.

    Another (private) approach would be using GreaseMonkey (or the equivalent of other Browsers) to manipulate the CSS...

    Beside of this it's really nice to navigate through the new site! 8-)

    Cheers Rolf

Re^2: Major update to
by ELISHEVA (Prior) on Jul 19, 2009 at 01:42 UTC

    I want to echo the concern about the 'floating' top bar, but from a slightly different angle. I am slightly dyslexic and the floating toolbar aggrevates a problem I already have following the flow of text lines.

    To avoid losing my place in the text, I am in the habit of focusing on a particular position within the page and then scrolling to page to see additional lines (rather than reading down the page and then scrolling a whole pageful at a time when I hit the bottom). On the old perldoc site, I was in full control over how much text scrolled into view. This is not so for the new perldoc site layout.

    Whether I focus on the top or middle of the page I seem to run into problems. If I focus on the top, the floating top bar has a habit of cutting lines of text in half (rather than moving line by line). If I focus on the middle, I sometimes notice that, from time to time, there is a rectangular region of text on the right (about 10 lines long and half a line wide) that seems to lag behind and momentarily refuse to scroll at that same time as the text to the left. There is little I can do to control this so my eyes have to jump back and forth sometimes skipping forward half a line and sometimes not. (In case this is a browser-specific issue, browser is Firefox: 3.0.11, Javascript enabled)

    If there is a way to insure that the floating bar does not cut lines of text in half that might go a long way to making it more comfortable for certain readers. Otherwise, I think one should look at other ways to make "tools" accessible. Floating sidebars, perhaps?

    Best, beth

    Update:It appears the flicker in the middle is unrelated to the floating header. It also is only visible for certain usages of scrolling. To see it: keep your eye focused on the middle of the page and scroll using slide rather than page down, space or click - there is a box on the right that "wobbles", "flickers" as you scroll.

    As for the floating header, if you are using firefox, you can remove it by installing the firefox extension Stylish and the style Pin the Perldoc Header down. Many, many thanks to the monks in the CB and especially hobbs who wrote the style. See -- keep the navigation header out of your way for more information.

Re^2: Major update to
by hobbs (Monk) on Jul 22, 2009 at 05:45 UTC
    I've posted a user CSS snippet to disable the "floaty bar" at; it can be found here.
Re^2: Major update to
by jj808 (Hermit) on Jul 28, 2009 at 18:27 UTC

      Much better: The site is usable again now.

      Do count me as one that liked the old design better though: while I appreciate some of the new navigation options (direct links to Perl version docs and module docs are nice), the overall color scheme, and the fixed width, are steps far backward in my opinion. You've gone from a welcoming and cheery site, to an forbidding institutional one.

Re^2: Major update to
by LanX (Sage) on Jul 28, 2009 at 19:42 UTC
    Another slightly distracting aspect of the fixed floating bar is that it's hindering text searches. The result of a backward search is normally scrolled to the top window border. It's really confusing to know there are hits but not to find them, because they are covered by the bar...

    UPDATE: Just set the position to "Standard" in, which really works fine! 8)

    But testing reveals a strange phenomenon in FF3: While backward searching for "Comma" in perlop the second hit is not visible, because 2 lines at the top are not shown...

    I'm completely clueless how to produce this effect. Does anyone else observe it?

    Cheers Rolf

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://781123]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (1)
As of 2022-10-07 03:07 GMT
Find Nodes?
    Voting Booth?
    My preferred way to holiday/vacation is:

    Results (29 votes). Check out past polls.