Bug 60109 - Long strings in <entry> do not scroll, the cursor/carat becomes invisible to user on IOS
Summary: Long strings in <entry> do not scroll, the cursor/carat becomes invisible to ...
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.4.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-10 23:14 UTC by cd12172
Modified: 2017-10-11 14:14 UTC (History)
2 users (show)

Tags: cursor, Entry, ios
Is this bug a regression?: Yes
Last known good build:


Attachments
Working behavior (317.77 KB, image/gif)
2017-10-10 23:28 UTC, Paul DiPietro [MSFT]
Details
app.xaml (1.41 KB, application/xaml+xml)
2017-10-11 01:37 UTC, cd12172
Details
screen shot (170.58 KB, image/png)
2017-10-11 01:38 UTC, cd12172
Details
video (526.66 KB, video/mp4)
2017-10-11 01:54 UTC, cd12172
Details
Working behavior -- second reproduction attempt (583.22 KB, image/gif)
2017-10-11 02:52 UTC, Paul DiPietro [MSFT]
Details
updated screen capture (4.31 MB, video/mp4)
2017-10-11 14:14 UTC, cd12172
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 60109 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description cd12172 2017-10-10 23:14:08 UTC
When entering a string into a <Entry> control, the cursor falls out of user view to the right.  The string is collected, but entry is cumbersome.

Expected behavior is:
cursor starts on left side.
Moves right as data is entered.
Once the cursor gets to the visible right edge of the <entry>, data should shift left as data typed (or entered by auto correct).  This would mean the cursor stays at the right visible edge as one types.

I have read other bugs that relate to embedded controls.  This is basic.  This code reproduced the problem

  

<?xml version="1.0" encoding="utf-8" ?>
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             x:Class="MyYard.Views.bugzilla">
    <ContentPage.Content>
        <StackLayout>
            <Label Text="Welcome to Xamarin Forms!" />
            <Entry></Entry>
        </StackLayout>
    </ContentPage.Content>
</ContentPage>
Comment 1 Paul DiPietro [MSFT] 2017-10-10 23:27:40 UTC
You will need to be more specific about device(s) you're experiencing this on. I have just used that baseline code and the Entry cursor does not disappear on an iOS 11 simulator. I am attaching a GIF of the attempted reproduction.
Comment 2 Paul DiPietro [MSFT] 2017-10-10 23:28:12 UTC
Created attachment 25260 [details]
Working behavior
Comment 3 cd12172 2017-10-11 01:37:40 UTC
Created attachment 25262 [details]
app.xaml
Comment 4 cd12172 2017-10-11 01:38:26 UTC
Created attachment 25263 [details]
screen shot
Comment 5 cd12172 2017-10-11 01:39:43 UTC
written on PC running VS 2017 community

compiled on Mac 10.12.6
run in simulator (also on iphone 6 with ios 11) - all do the same thing

pic attached.  in it you see the cursor, and auto correct suggesting a word you cannot see on the
Comment 6 cd12172 2017-10-11 01:54:42 UTC
Created attachment 25264 [details]
video
Comment 9 Paul DiPietro [MSFT] 2017-10-11 14:09:33 UTC
Okay, there was a package issue going on and this is explicitly a 2.4 issue. When filing these reports, please make sure to mark whether these are regressions.
Comment 10 cd12172 2017-10-11 14:14:14 UTC
Created attachment 25271 [details]
updated screen capture

Attached updated screen capture - shows UWP and ios side by side.  Only happens on ios (simulator and device).