Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TIMOB-24753]: iOS View sizes are incorrect in 6.1.0.GA (regression) #9120

Merged
merged 2 commits into from Jun 9, 2017

Conversation

vijaysingh-axway
Copy link
Contributor

@htbryant94 htbryant94 self-requested a review June 7, 2017 15:26
Copy link
Collaborator

@hansemannn hansemannn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the ticket that implemented the bounding-rect usage works with this solution. But please note that the maxSize property was there for another reason, see the 480px check in it's declaration. I am still validating that case, but QE can already proceed with their tests. Required label-tests are:

  • horizontal / vertical layout
  • auto-width (FILL and SIZE) / percentages / static values
  • label container that size different than the children / label
  • left / right usages

We may want to create an own layout-focussed QE-app if we don't have so far. This kind of changes are always too sensitive to test with only 1-2 test-cases.

Copy link

@htbryant94 htbryant94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved! View sizes are now calculated correctly when using percentages. Additionally, performed tests related to the following parameters:

  • horizontal / vertical layout
  • auto-width (FILL and SIZE) / percentages / static values
  • label container that size different than the children / label
  • left / right usages
  • Portrait / Landscape Orientations

Tested on Device and Simulator.

@htbryant94 htbryant94 merged commit b935d79 into tidev:master Jun 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants