Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    You found a bug! We've classified it as TOUCH-2704 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    6
    Vote Rating
    0
    amikhailau is on a distinguished road

      0  

    Default CRITICAL: LONG FORMS ARTIFACTS with Form Assistant on iOS make a form unscrollable

    CRITICAL: LONG FORMS ARTIFACTS with Form Assistant on iOS make a form unscrollable


    By creating a simple fullscreen form which contains approximately 3 times the height of an iPhone number of fields, using form assistant ("prev/next") on iOS causes rendering artifacts such as:

    moving down with the "next" button, the focus jumps quite a few fields down once it reaches the fields that were not part of the viewport which causes the bottom of the form to expand to about additional 3/4 of the screen height and the form becomes no longer fully scrollable to the top.

    The prev/next jumping can easily be illustrated by pointing your iPhone device to http://dev.sencha.com/deploy/touch/examples/production/kitchensink/#demo/forms

    and clicking next, next, next.... you will also see a blinking cursor artifact once you start scrolling a form while a field is focused and by hitting prev, prev, prev the scrolling area gets completely out of sync.

  2. #2
    Sencha - Sencha Touch Dev Team Jacky Nguyen's Avatar
    Join Date
    Jul 2009
    Location
    Palo Alto, California
    Posts
    469
    Vote Rating
    14
    Jacky Nguyen has a spectacular aura about Jacky Nguyen has a spectacular aura about

      0  

    Default


    It's a well-known bug with iOS Safari. There's nothing we could do other than waiting for Apple to fix it.
    Sencha Touch Lead Architect

  3. #3
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    6
    Vote Rating
    0
    amikhailau is on a distinguished road

      0  

    Default


    We have yet to replicate it on a basic (all visible fields) html5 form in mobile safari so we believe this has got something to do with the way Sencha handles visibility of the fields of the fields are outside the viewport.

  4. #4
    Sencha - Sencha Touch Dev Team Jacky Nguyen's Avatar
    Join Date
    Jul 2009
    Location
    Palo Alto, California
    Posts
    469
    Vote Rating
    14
    Jacky Nguyen has a spectacular aura about Jacky Nguyen has a spectacular aura about

      0  

    Default


    Try to translate an input after it's already focused, i.e change left / top style value or use CSS transform. On iOS, also try using -webkit-overflow-scrolling: touch to make a long form scrollable, focus on an input, then scroll up / down. You'll easily see the same issue.
    Sencha Touch Lead Architect

  5. #5
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    6
    Vote Rating
    0
    amikhailau is on a distinguished road

      0  

    Default


    This is definitely consistent with both Android and iOS. The bug is in the approach Sencha takes to render form elements. If the element is not part of the view port and has not been rendered (which it looks like it is hidden by sencha rendering mechanism), the next button is not present.
    We also have seen catastrophic artifacts on Android for when you would click out of a field to scroll down to the next field manually because "Next" button or "Tab" button on the android is not enabled for an unrendered field, and the portion of the screen that was hidden by the keyboard would remain white and cut off the whole viewport for the rest of the application even if you navigate away to a different controller action and render a different view.

    Guys, I think it's worth re-considering this lazy rendering mechanism for input fields because it is rendering horrific artifacts not suitable for commercial production apps.

    Also, Android support proves to be very poor. For example, we found in your source code, inside 'Ext.navigation.View' a hard-coded downgrading of functionality for Android:

    /**
    * @private
    * Disable all animations on Android
    */
    applyLayout: function(config) {
    config = config || {};


    // TODO: This should be a configuration
    if (Ext.os.is.Android) {
    config.animation = false;
    }


    return config;
    },

    How do you explain such hard-coding for a non-beta product which is advertised to work cross-platform?

    Thank you.

  6. #6
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    6
    Vote Rating
    0
    amikhailau is on a distinguished road

      0  

    Default


    Here are the screenshots to demonstrate the behaviour:

    I. Please note an artifact of the viewport adjustment to display the keyboard (it does it inconsistently, there are times when it works).

    II. Demonstrates normal behaviour - you are inside the input field and the next field is present: next button is enabled.

    III. You are inside an input field and there is a next field present in the view (as demonstrated in screenshot V) but no next field ("city") is rendered yet.

    IV. When the keyboard goes away, the viewport is stuck displaying only half of the screen which is demonstrated by the white empty background.Capture.jpgCapture2.jpgCapture3.jpgCapture4.jpgCapture5.jpg

  7. #7
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    6
    Vote Rating
    0
    amikhailau is on a distinguished road

      0  

    Default Please provide feedback about white area artifacts

    Please provide feedback about white area artifacts


    Please provide feedback about white area artifacts

  8. #8
    Ext JS Premium Member
    Join Date
    Feb 2011
    Posts
    6
    Vote Rating
    0
    amikhailau is on a distinguished road

      0  

    Default Here's another example of a long form

    Here's another example of a long form


    Here's another example of a loooong form behaving terribly with the next button

    http://maalguru.in/touch/Raxa/src/registration/

  9. #9
    Sencha Premium Member
    Join Date
    Sep 2012
    Posts
    4
    Vote Rating
    0
    Creyke is on a distinguished road

      0  

    Default


    Hi guys,

    Just wondering if there has been any movement on this bug. It's been open for almost a year now, and there's still forum posts popping up reporting instances of it, such as http://www.sencha.com/forum/showthread.php?260856-Android-and-iOS-issues-with-scrollable-form

    I
    s there any ETA on a fix? This is causing us some real problems at the moment.

    Thanks

Thread Participants: 2

Tags for this Thread