Results 1 to 3 of 3

Thread: TextArea Field not showing scrollbars

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1

    Default TextArea Field not showing scrollbars

    ]Ext version tested:
    • Live version, 2.3.0
    Browser versions tested against:
    • iOS7 Safari on iPhone 4S
    • User is unable to scroll in TextArea field
    Steps to reproduce the problem:
    • Open the Kitchen Sink app in iOS7 Safari, add to home screen, and then open it from the icon.
    • Go to User Interface > Forms.
    • Scroll down to one of the text Area fields, e.g. Bio, and tap inside the box. Now type randomly untill it fills completely and conitinue to type. Nowgoto first line of textfield
    The result that was expected:
    • There should be scroll bar that scroll textfield to first line so that user can user finger to point where he wants to insert new words.
    The result that occurs instead:
    • The user has no scroll bar, he has to go either via magnifier glass or using arrow key. This looks ridiculous if its more then one page.
    Manish Kumar

  2. #2
    Sencha - Support Team
    Join Date
    Oct 2011


    Thank you for the report this is a known issue TOUCH-1941.
    Here is a suggested workaround on the original post reporting this issue. I have not tested this personally but some users have had success with it:
    I have bumped the jira ticket to let engineering know that this issue still exists.
    Get more personalized support via a support subscription.

    Need more help with your app? Hire Sencha Services [email protected]

    When posting code, please use BBCode's CODE tags.

    Need to include a test case use:
    The official Sencha Fiddle

  3. #3
    Sencha User =NR='s Avatar
    Join Date
    Mar 2013


    how exactly is to use those workaround fix that override sencha's default code??
    just create a new file and put it somewhere in app folder ?
    so many of override patch suggested yet none of explaining how to implement it...

    anyway just want to point out if that is the suggested work around why is this bug still happens in ST 2.3.1 ?
    considering that the issue exist since ST 2.0.0

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts