autocomplete: dropdown opens to the top after upgrade to 1.1.13

[rreitmann]

Bug:

After upgrading from 1.1.12 to 1.1.13 all autocompletes open to the top instead of to the bottom.

Steps to reproduce the issue:

Detailed Reproduction Steps:

Open https://material.angularjs.org/1.1.12/demo/autocomplete and https://material.angularjs.org/1.1.13/demo/autocomplete and compare the position of the dropdown of the first autocomplete.

What is the expected behavior?

Without specifying md-dropdown-position I expect the dropdown to open to the bottom and only if there is not enough space in the viewport open to the top...

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

• AngularJS: 1.7.7
• AngularJS Material: 1.1.13
• OS: Ubuntu
• Browsers: Chrome

[Splaktar]

It seems like the check has always defaulted to the top if there was room:

In v1.1.12:

material/src/components/autocomplete/js/autocompleteController.js

Lines 141 to 144 in e01f340

	// Automatically determine dropdown placement based on available space in viewport.
	if (!position) {
	position = (top > bot && root.height - top - MENU_PADDING < dropdownHeight) ? 'top' : 'bottom';
	}

In v1.1.13:

material/src/components/autocomplete/js/autocompleteController.js

Lines 144 to 147 in 38fb991

	// Automatically determine dropdown placement based on available space in viewport.
	if (!position) {
	position = (vrect.top + MENU_PADDING > dropdownHeight) ? 'top' : 'bottom';
	}

It's just that the calculation was updated as part of the fix from @marosoft for dropdowns showing up on top even when there was no room (#10859).

We weren't able to find anything in the Material Design and HTML specs that specified this. There was some discussion of this in PR #11629.

As you are the second person to report this, we should consider changing the default to bottom now that this new calculation is in place. I think that it better aligns with what people generally expect.

[rreitmann]

@Splaktar IMHO people expect a dropdown not a "dropup" and furthermore they got used to that behavior in the former versions...