Scrollbar disappears on Safari

If it's a bug, you can report it through your browser's help menu.

I have had this same problem. But when I quit and relaunch Safari the scrollbar reappears. Many times when I quit Safari a 'crash warning' appears. Are these common problems for many users?

Many times when I quit Safari a 'crash warning' appears. Are these common problems for many users?

Of course not.

Firstly, update your OS to 10.4.11 and get the latest Safari, then try this:

Repairing permissions is an important part of regular maintenance, and should always be carried out both before and after any software installation or update.

Go to Disk Utility (this is in your Utilities Folder in your Application folder) and click on the icon of your hard disk (not the one with all the numbers).

In First Aid, click on Repair Permissions.

This only takes a minute or two.

Background information here:

http://docs.info.apple.com/article.html?artnum=25751

and here:

http://docs.info.apple.com/article.html?artnum=302672

If you were having any serious problems with your Mac you might as well complete the exercise by repairing your hard disk as well. You cannot do this from the same start-up disk. Reboot from your install disk (holding down the C key). Once it opens, select your language, and then go to Disk Utility from the Utilities menu. Select your hard disk as before and click Repair.

Once that is complete reboot again from your usual start-up disk.

More useful reading here:

Resolve startup issues and perform disk maintenance with Disk Utility and fsck

http://support.apple.com/kb/TS1417

I have the same problem on both a iMac G5 and my Macbook 13 inch. I regularly run Cocktail and repair permissions often. Same thing happens on both. I will be using Safari and randomly the scroll bar disappears and I have to restart Safari. I am running 10.4.11 and Safari 3.1.2
Obviously it is not a permissions problem nor a fix by disk utility or even Drive Genius can fix.
This never happens with Firefox.

What gives Apple?

BruceR said:
"I have had this same problem. But when I quit and relaunch Safari the scrollbar reappears. Many times when I quit Safari a 'crash warning' appears. Are these common problems for many users? "

I am also experiencing this. I am running 10.5.4 on a 1.25GHz PowerPC G4 with 1.25Gb DDR SDRAM.
Safari is v3.1.2. I regularly perform permissions repair and MacJanitor maintenance.

If anything I can vaguely recall being a pattern, but without disciplined methodical verification,
is that IIRC the vertical scroll bar disappears AFTER I have followed a link to a .PDF that
opens in Acrobat (current version is v7.0.5).

This is most annoying!

Craig

Hello and Welcome to Apple Discussions ...

Follow Klaus1's suggestions... if the scroll bar issue persists, try this.

Quit Safari. Now locate this file: com.apple.safari.plist
It's here: /Users/YourName/Library/Preferences. Open the Preferences folder and drag that file to the Desktop. Launch Safari and see if your scroll bar functions as it should. If it does, then the pref file you dragged to your Desktop is corrupted. Drag it to the trash, empty the trash and reboot. Your Mac will create a new Safari preference file for you.

Carolyn 🙂

Carolyn suggested:
" . . . Quit Safari. Now locate this file: com.apple.safari.plist
It's here: /Users/YourName/Library/Preferences. Open the Preferences folder and drag that file to the Desktop. Launch Safari and see if your scroll bar functions as it should. If it does, then the pref file you dragged to your Desktop is corrupted. Drag it to the trash, empty the trash and reboot. Your Mac will create a new Safari preference file for you. "

Thank you, Carolyn. I will keep this advice handy.
Meanwhile, I JUST updated Adobe Reader to 9.0.0 and OS X to 10.5.5, so I will see if problem persists.

c²

Hi Carolyn,

Thanks for the post. So far so good. Good to have you remind us about the plist files. How many times I have had a corrupt plist file with many other applications but failed to think of it in this case.
Thank you!

Thanks Carolyn S., I certainly give that a try next times the problem occurs. Heretofore the only thing that has worked was a restart; however, not only is that a pain, according to several comments I've read in trying to solve this, it seems to not always solve the problem (though, knock on wood, thus far it's worked 100% of the time for me).