question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Enhancement for autocomplete & datepicker: allow for positionning the options/calendar panel elsewhere than next to the input

See original GitHub issue

Bug, feature request, or proposal:

Proposal for enhancement for autocomplete & datepicker

What is the expected behavior?

Panel for autocomplete options or datepicker calendar can be positionned elsewhere than next to their related input field.

What is the current behavior?

Panel for autocomplete options or datepicker calendar cannot be positionned elsewhere than next to their related input field.

What are the steps to reproduce?

<div fxLayout="row">
  <div fxFlex="50">
    <form [formGroup]="formStatus.form">
      <div>
        <md-input-container>
          <input mdInput placeholder="Address" [mdAutocomplete]="auto" formControlName="address">
        </md-input-container>
      </div>
    </form>
  </div>
  <div fxFlex="50" style="background-color: palegreen">
    <!-- options panel should appear here in the palegreen div -->
    <md-autocomplete #auto="mdAutocomplete" [displayWith]="addressFormatter">
      <md-option *ngFor="let address of addresses | async" [value]="address">
        {{ address.description }}
      </md-option>
    </md-autocomplete>
  </div>
</div>

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

Autocomplete and datepicker usage will be more flexible

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Angular material: 2.0.0-beta.6

If I am wrong and this feature is currently available, maybe a update to the documentation would be worthwhile.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:7
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

4reactions
willshowellcommented, Jun 20, 2017

Seems like this could be useful for a search like inbox’s screen shot 2017-06-20 at 9 15 49 am

3reactions
renestaldercommented, Oct 10, 2017

For a start, I would be happy to deactivate the automatic positioning based on space. Like having an option for positioning:

  • auto: Current behavior
  • bottom: force to always show below the input field
  • top: force to always show above the input field
  • custom: What this whole issue ticket is suggesting
Read more comments on GitHub >

github_iconTop Results From Across the Web

Solved: Datepicker Calendar Control - Positioning
Specifically, the position of the calendar will always be near the top ... Another option is to enable the experimental feature "Enable app ......
Read more >
Designing The Perfect Date And Time Picker
In a nutshell, it's a good idea to prepopulate the dates only if you are certain that the user is likely to choose...
Read more >
How to change the pop-up position of the jQuery DatePicker ...
To get around that, simply set the position using setInterval. The current script will complete, showing the datepicker, and then the repositioning code...
Read more >
Limitless - Responsive Web Application Kit by Eugene Kopyov
The datepicker is tied to a standard form input field. Focus on the input (click, or use the tab key) to open an...
Read more >
Component and widget descriptions and settings - IBM
Optional. This field represents the initial date selected on the pop-up calendar when the host application does not pre-fill the associated input field...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found