Regarding LJ cuts...

[author_by_night]

Does anyone elses's LJ scroll immediately to the first or second paragraph when clicking on fic cuts?

Because I just asked someone to keep in mind that LJ does that, (the fic was R), only to then realize, judging by her and someone elses's reactions, that not everyone's LJ does do that.

I feel bad now, and a little annoyed. Is it my computer, or LJ being stupid?

Comments

[chocolatepot.livejournal.com]

Mine scrolls immediately to where the cut is placed.

[raggedass-road.livejournal.com]

That's what mine does. It's sort of annoying.

[parallactic.livejournal.com]

Ditto. I figure it's because we're already supposed to have read the stuff above the cut, so when we click, we can get on with reading the stuff below the cut without having to scroll down.

[gileonnen.livejournal.com]

My computer does that when I open a cut in a new window (or tab in Firefox)--mainly a new window, though. Usually, web browsers will open a new window as a smaller window, and when I maximize the window, the cut jumps because LJ identifies it with a location on screen rather than with a location in the text. Or so it seems.

Is that anything like your situation?

[tunxeh.livejournal.com]

Does anyone elses's LJ scroll immediately to the first or second paragraph when clicking on fic cuts?

That's what the "#cutid" part of the URL is supposed to achieve. But it's not working for me much lately (using Safari); LJ goes through a sequence of redirections from one URL to another as part of their recent security changes and as it does so everything after the # is lost and I just end up with the bare URL, and my browser goes to the top of the entry.

[partly-bouncy.livejournal.com]

For me, LJ cut tag puts the top line at the very top. It doesn't go down further but the natural inclination is sometimes to read what is more eyeball center than the top of the page.