Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • J JVFloatLabeledTextField
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jared Verdi
  • JVFloatLabeledTextField
  • Issues
  • #177
Closed
Open
Issue created Sep 14, 2017 by Matthew Carr@MattCarr147

A TextView with a multiline placeholder does not display correctly when 'scrollEnabled' is set to false.

NOTE: The constraints used in the demo project do not work particularly well when setting descriptionField.scrollEnabled = FALSE, so please forgive the odd style of the following screenshots. The important thing is the Description field.

Due to #176, I needed to place a JVFloatLabeledTextView within a UIScrollView. For reference, an example of the layout I am working towards is as follows:

simulator screen shot - iphone 7 - 2017-09-14 at 16 01 53

In order to achieve the view using AutoLayout and to avoid confusing nested scrolling behaviour, I found it easiest to disable scrolling on the TextView. Unfortunately, the view is not rendered correctly when using a multiline placeholder. For example:

simulator screen shot - iphone 7 - 2017-09-14 at 16 27 15

The expected result is as follows (again, forgive the odd constraints behaviour):

simulator screen shot - iphone 7 - 2017-09-14 at 16 28 55

I've been working on a fix which, as far as I can tell, addresses this issue without affecting existing behaviour. I'll submit a pull request shortly.

Assignee
Assign to
Time tracking