Currently Being ModeratedMar 18, 2013 12:41 PM (in response to Shawn McCuan)
I've reported the same bug before on this discussion.
As sad as it seems as I am a HUGE Apple fan, I am seriously considering switching to Chrome.
Processor 2,6 GHz Intel Core i7
Memory 8 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 650M 1024 MB & Intel HD Graphics 4000 384 MB
Software OS X 10.8.2
Safari Version 6.0.2 (8536.26.17)
Currently Being ModeratedMar 18, 2013 12:46 PM (in response to adriaanf)
I had rendering issue in Safari on my MacBook Pro mid 2010 Core i7
Earlier, disabling Automatic Graphics switching did resolve this issue.
After updating to 10.8.3, I've enabled back Automatic Graphics Switching and haven't seen rendering issues in Safari anymore.
So, for those strugglers, who're still blaiming on 10.8.2 - just update to 10.8.3.
Currently Being ModeratedMar 19, 2013 10:50 AM (in response to Shawn McCuan)
Problem still happening here (late-2011 15" high-end MBP), though not as often as it was originally. Today I noticed something that may or may not be of use: I was posting to a forum and accidentally double tapped on the text area with the Magic Mouse, hwich caused Safari to do a smart zoom on that, and as a result the cursor stopped blinking, started to disappear, and the rendering issues were all back until I pinched on the trackpad to zoom all the way out again. I never use zoom in Safari, so this may be the reason why I seldom see any rendering issues anymore, but they're definitely still happening.
Currently Being ModeratedMar 19, 2013 12:02 PM (in response to Vaelian)
You guys really need to point out whether or not you've updated your machines to the latest software, 10.8.3 and Safari 6.0.3 are available and they should have addressed these problems. They have done so for me on my rMBP I got last month. When I got it with 10.8.2 and 6.0.2 loaded the glitches drove me nuts too, but I haven't seen them since I got on 10.8.3. Now it may be possible that somewhat older models have something different about them, but the culprit really seems to be something specific to HD 4000 graphics drivers.
Like I and many others have mentioned before, using gfxcardstatus switcher to force the Nvidia GPU usually puts an end to the issue, and this is why I say it is probably an issue with the Intel iGPU driver or other software that interacts with it in some capacity.
Registered OS X developers have been reporting issues with the update long before it went public. I haven't experienced issues as annoying as when I posted originally for a very long time, but that doesn't mean they're gone, as sometimes I still notice them with a fully updated system. Just selecting a product at the Apple Store website and then scrolling all the way to the bottom at certain browser window sizes is enough to see the Summary box on the right flicker while scrolling back up, which is one of the rendering issues.
Currently Being ModeratedMar 19, 2013 12:29 PM (in response to Vaelian)
Also, just wanted to add something else.
Just because these issues happen predominantly on the Intel driver alone, doesn't mean they are related to that driver in particular, because the test that I mention above also causes flickering when the dedicated GPU is enabled. The way I see it is: WebKit is invoking some kind of undefined behavior somewhere in the code, and while the dedicated GPUs' drivers may behave sanely under those circumstances so as to minimize rendering artifacts caused by the incorrect use, the Intel driver may not. As evidence supporting this theory, the test that I mentioned previously with the Apple Store website causes flickering on both the dedicated and integrated GPUs.
It isn't fixed because the problem you're seeing is completely unrelated to everything else described in this thread.
In my experience, the other problems discussed in this thread (disappearing and reappearing text while typing, situations where the right half of a paragraph of text fails to scroll, etc.) seem to occur only in Safari on recent MacBook Pro hardware, and only when the Intel GPU is enabled.
By contrast, I can see what you're describing in Chrome on my six-year-old iMac, which has never exhibited either of the other problems, in and doesn't even have an Intel GPU.
I would suggest sending feedback to the Apple Store customer service team and reporting the quirky summary pane behavior if it bothers you. If what you're describing is a browser bug at all, it is definitely not the same browser bug.
Currently Being ModeratedMar 19, 2013 1:22 PM (in response to David A. Gatwood)
> It isn't fixed because the problem you're seeing is completely unrelated to everything else described in this thread.
Both of these were happening a lot when Mountain Lion was released with Safari 6. You can see my own posts to this thread all the way to page 2, and if still in doubt about the issue discussed in this thread, consult the original post.
> In my experience, the other problems discussed in this thread (disappearing and reappearing text while typing, situations where the right half of a paragraph of text fails to scroll, etc.) seem to occur only in Safari on recent MacBook Pro hardware, and only when the Intel GPU is enabled.
Which is why I mentioned a problem related exclusively to zooming on Safari earlier, it may explain why the text rendering issues are more common on Retina MacBook Pros. That said, parts of pages not being displayed by scrolling very quickly is not an uncommon occurrence here, and add-ons such as Awesome Screenshots have lost their ability to capture entire pages as a result, because they need to scroll very fast in order to achieve that. Finally, just because you see text rendering issues mostly while using integrated graphics, that doesn't mean the problem is in any way related to that hardware or its driver, as I explained previously when I mentioned the possibility of undefined behavior being invoked by WebKit.
> By contrast, I can see what you're describing in Chrome on my six-year-old iMac, which has never exhibited either of the other problems, in and doesn't even have an Intel GPU.
A WebKit browser displaying WebKit rendering issues... How unexpected...