select: dropdown position is wrong in iOS Safari

[pavelsl]

Bug:

CodePen and steps to reproduce the issue:

CodePen Demo: usage with flexbox grid

CodePen Demo: usage with floating grid (tried to see if issue reproducible if we are not using flexbox)

CodePen Demo: almost no custom css (no grid at all)

Detailed Reproduction Steps:

1. Clear device browser cache and data
2. Open jsbin link
3. Scroll a page down
4. Open dropdown

What is the expected behavior?

md-select dropdown in place

What is the current behavior?

md-select dropdown is not in place

What is the use-case or motivation for changing an existing behavior?

Which versions of AngularJS, Material, OS, and browsers are affected?

• AngularJS: 1.6.8
• AngularJS Material: 1.10.0
• OS: iOs 11.x
• Browsers: Safari

Is there anything else we should know? Stack Traces, Screenshots, etc.

Some times issue is not reproducible but after clearing cache it present again. It's really not too hard to reproduce.

[pavelsl]

@Splaktar Might this will be interesting for you.

[pavelsl]

It would be great to have any method to trigger recalculation of md-select dropdown position.

[codymikol]

This seems to work fine for me on iOS 11.x

[Splaktar]

@pavelsl Can you please provide the device model? iPhone 5, 8, X, etc.

[pavelsl]

@Splaktar
I believe any not the newest device (which is slower than iPad Pro @codymikol's ) as the issue.

I have two iPad's mini.
Exact iOs version of iPad mini first has v10.1.1 & iPad mini second has v11.3. And the issue is reproducible on both of them. Screenshots are taken on v10.1.1

Can check on old iPad 2 as well which has iOs v9.x

---

I was able to fix this by additional position check which happen with 1-2s delay. It seems that md-select dropdown position calculation logic doesn't work well on these. Not sure because of logic issue, or device mobile safari glitches.

---

PS:
@pavelsl Can you please provide the device model? iPhone 5, 8, X, etc. Have you seen screenshots?

[Splaktar]

I tested on an iPad Air simulator with iOS 11.4 and I was not able to reproduce these issues. Unfortunately I don't have any iOS devices to test against.

I don't think that testing on an iOS 9 device is worthwhile since we don't suppport iOS 9 at this time. You can find some details about browser support here.

If you can test a fix locally and verify that it solves the issue, I would be happy to review the PR.