[code] blocks missing scrolling on iPads

Discussion in 'Site and Forum Feedback' started by dejo, Apr 5, 2010.

  1. dejo Moderator


    Staff Member

    Sep 2, 2004
    The Centennial State
    Code blocks that normally display scroll-bars, as needed, don't have any such mechanism using Safari on the iPad. See the attached screenshot for a sample:

    Attached Files:

  2. Doctor Q Administrator

    Doctor Q

    Staff Member

    Sep 19, 2002
    Los Angeles
    The same problem happens on the iPhone. It appears to be a bug in the mobile version of Safari.

    The vBulletin forum software specifies a fixed-height box with the overflow:auto property, which tells the browser to include a scollbar if the content doesn't fit, and no scrollbar otherwise. But no scrollbar shows up, so the bug seems to be on the browser side, not on the MacRumors side.

    If you copy the code block and paste it into a text application, you'll see all of it, but that makes a lousy workaround. A better workaround is to reply to the post; you'll find the full content in the message area.
  3. belvdr macrumors 603

    Aug 15, 2005
    No longer logging into MR
    I was reading on Slashdot today that another person had issues with the iPad and some frames not showing scrollbars. I would have thought that would have been fixed by now.
  4. kainjow Moderator emeritus


    Jun 15, 2000
    I doubt Apple is going to add scroll bars to inline frames and areas like this when it hasn't been added after all this time.

    A potential fix would be to open a new window when the user taps that area and display the code there. Probably could be done with JavaScript I imagine.
  5. irmongoose macrumors 68030


    Dec 3, 2001
    Sometimes Tokyo, sometimes California
    I disagree. With the iPhone/iPod touch, most people would dismiss such an error due to it being a "mobile" version of the web, regardless of how much Apple touted it as more than that.
    With the iPad, however, there just is no excuse. This isn't a Flash-like issue. It's a matter of Safari being standards-compliant and rendering HTML code properly.
    They better get working on it, because it's a bug, nothing else.


Share This Page