Previous 1 12 13 14 15 16 Next 239 Replies Latest reply: Apr 22, 2013 2:50 AM by bluejay0018 Go to original post
  • BSpiros Level 1 (0 points)

    My thoughts exactly!!!

  • slu4 Level 1 (0 points)

    I can't find the 10.8.3 developer preview on the Apple Dev Center site. Do I need to be a Mac developer to get access to this link?

     

    I did pay to be an iOS developer but no way I'm gonna pay another $99 (on top of how much of a share of my pocketbook APPL already enjoys)

  • David A. Gatwood Level 3 (580 points)

    Yes, seeds are typically available only to members of the relevant developer program.  If you have access to seeds, they would typically show up below Xcode in the Downloads pane.  If you don't see a seed, that either means there isn't one available for that OS at that time or you don't have access to it.

  • LOLuMad Level 1 (5 points)

    This started as soon as I upgraded to Mountain Lion. I never had this issue with Snow Leopard or Lion on this MacBook Pro. Chrome works fine, no redraw issues so I know it's Safari/Mountain Lion. I'm surprised this has gone for as long as it has without Apple addressing this issue.

     

    Here's a video a made a while back of it: http://www.youtube.com/watch?v=nA8EeZCVnQ4

  • slu4 Level 1 (0 points)

    I have not seen the terrible rendering issues since updating to the 10.8.3 builds (found links for them on a site called shade.sh) so at least we'll get a fix with 10.8.3. I still have this problem though. http://stackoverflow.com/questions/14914650

  • LOLuMad Level 1 (5 points)

    Based on that link you posted, 10.8.3 will NOT resolve the issue:

     

     

    • Safari Version 6.0.3 (8536.28.10) on Mountain Lion 10.8.3 12D68 (Retina Macbook Pro 15.4") still suffers from this issue.

     

    Guess it's back to Google Chrome.

     

    Thanks Apple.

  • slu4 Level 1 (0 points)

    Yeah but you didn't read it closely enough, the rendering issues specific to the one you made a video about are already fixed in these new 10.8.3 builds, however the other CSS3 related bug (which you will notice I was the poster of the Stackoverflow question) is not addressed but I can say that at least on my machine the weird-*** flickering of page sections have not come back.

     

    On a rMBP Safari is pretty much the only pleasant browser to use due to the GPU acceleration: every other browser including Chrome scrolls super slow and is worse for battery life due to the CPU being overburdened by rendering pages at the ridiculous display resolution.

  • Carl James Level 1 (10 points)

    10.8.3 did not fix this issue for me, but it "seems" like it may now be fixed after the SMC firmware update that just came out on February 12th. Although the problem is not mentioned in the notes on the update...

     

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

     

    I have not had the problem since the 12th. Would any one else agree?

  • Carl James Level 1 (10 points)

    Actually, no... No it didn't fix it.

  • LOLuMad Level 1 (5 points)

    Nope, not fixed.

  • Krissypoo28 Level 1 (35 points)

    Screen Shot 2013-03-02 at 1.07.35 AM.png

     

    This is what I get. I just bought the 15 inch macbook pro (not retina) and it came with mountain lion os x. It is annoying but glad to know its a safari issue and not a hardware or software issue, or atleast I dont think so.

  • Breadman86 Level 1 (0 points)

    Yeah, I have that same graphical issue as well on various webpages, forms, etc. It's hugely annoying. I switched from Chrome to Safari a while back once I realized how nice Safari had become. Time to go back.

  • Krissypoo28 Level 1 (35 points)

    Yah but I like Safari though

  • Phaedon2 Level 1 (0 points)

    I seriously can't tell you how much this is ******* me off.  In fact, I can't even type this reply without major clipping of the text.  I am running the latest MBP 15" NR on 10.8.2. So amazingly disappointed.

  • LOLuMad Level 1 (5 points)

    I wonder if Apple pays attention to these discussions because I'm surprised it is taking them so long to address this issue. I know there's gotta be a couple of Apple employees who are on the higher end of the food chain who have experienced this issue. Come on Apple!