Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Entry is getting coverd by the Keyboard if you set TranslateY = -100 #3403

Closed
ederbond opened this issue Jul 26, 2018 · 2 comments
Closed

Entry is getting coverd by the Keyboard if you set TranslateY = -100 #3403

ederbond opened this issue Jul 26, 2018 · 2 comments
Labels
a/layout e/8 🕗 8 help wanted We welcome community contributions to any issue, but these might be a good place to start! inactive Issue is older than 6 months and needs to be retested p/Android t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!
Projects
Android Ready For Work

Comments

@ederbond
Copy link
Contributor

Description

Steps to Reproduce

  1. Download this reproduction case: https://github.com/ederbond/BugEntryVsKeyboard
  2. Run it on android
  3. There are two Entries on the page. Tap both of them,

Expected Behavior

I was expecting that when I tap the Entry's both of them I'll be repositioned above the keyboard.

Actual Behavior

The one I've set the TranslationY property gets covered by the keyboard.

Basic Information

  • Version with issue:

  • Last known good version:

  • IDE: Visual Studio 2017 Enterprise

  • Platform Target Frameworks:

    • iOS: 11.4
    • Android: 7.0

  • Android Support Library Version:
    Xamarin.Android.Support.v4 --- v27.0.2.1
    Xamarin.Android.Support.v7.AppCompat --- v27.0.2.1
    Xamarin.Android.Support.v7.CardView --- v27.0.2.1
    Xamarin.Android.Support.v7.MediaRouter --- v27.0.2.1

  • Nuget Packages:
    "Xamarin.Forms" Version="3.1.0.637273"

  • Affected Devices:
    SAMSUNG GALAXY TAB A (2016)

Screenshots

Reproduction Link

https://github.com/ederbond/BugEntryVsKeyboard
@pauldipietro pauldipietro added this to New in Triage Jul 26, 2018
@jassmith jassmith moved this from New to Ready For Work in Triage Jul 30, 2018
@ederbond
Copy link
Contributor Author

Hello @jassmith , do you guys have any news on this ?

@samhouts samhouts removed this from Ready For Work in Triage Oct 15, 2018
@samhouts samhouts added the inactive Issue is older than 6 months and needs to be retested label Mar 20, 2019
@samhouts samhouts added help-wanted up-for-grabs We welcome community contributions to any issue, but these might be a good place to start! help wanted We welcome community contributions to any issue, but these might be a good place to start! and removed help-wanted labels Jun 28, 2019
@samhouts samhouts moved this from To do to Inactive in Android Ready For Work May 21, 2020
@samhouts samhouts added this to the 5.0.0 milestone Aug 13, 2020
@samhouts samhouts added this to To do in vNext+1 (5.0.0) Aug 14, 2020
@samhouts samhouts removed this from the 5.0.0 milestone Nov 2, 2020
@jfversluis
Copy link
Member

Hope this is resolved by now 😬

Android Ready For Work automation moved this from Inactive to Done Nov 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
a/layout e/8 🕗 8 help wanted We welcome community contributions to any issue, but these might be a good place to start! inactive Issue is older than 6 months and needs to be retested p/Android t/bug 🐛 up-for-grabs We welcome community contributions to any issue, but these might be a good place to start!
Projects
Android Ready For Work
  
Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jassmith @jfversluis @samhouts @ederbond