Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

fix(typeahead): Scroll only parent element, not page #5212

Closed
wants to merge 2 commits into from

Conversation

deeg
Copy link
Contributor

@deeg deeg commented Jan 11, 2016

Closes #5180

Plunker demonstrating fix

Let me know if you want tests if this is a good solution. I can figure out a way to test it. FWIW does not look like this was being tested before.

@wesleycho
Copy link
Contributor

I'm fine with this approach - @Foxandxss what is your thoughts?

@Foxandxss
Copy link
Contributor

Fine for me, better if tested.

@deeg
Copy link
Contributor Author

deeg commented Jan 11, 2016

Sounds good, will add tests within an hour or so after I finish some work up.

Hope to make it into 1.0.1 if you don't mind waiting for an hour or two.

@Foxandxss
Copy link
Contributor

That is fine by me.

@deeg
Copy link
Contributor Author

deeg commented Jan 12, 2016

Just added tests.

Thanks @wesleycho & @Foxandxss for the feedback and getting this into 1.0.1

@wesleycho wesleycho added this to the 1.0.1 milestone Jan 12, 2016
@wesleycho wesleycho closed this in 3dac5e3 Jan 12, 2016
@icfantv icfantv changed the title fix(typeahead): Scroll only parent element, not apge fix(typeahead): Scroll only parent element, not page Jan 12, 2016
@frfancha
Copy link

The behavior of the last typeahead in the plunker with fix is quite strange: sometimes it opens several pixels under the input instead of just below as usual, and the "candidate" row is not highlighted in blue.
See attached print screen (windows 7, firefox ESR 38.4.0)
typeahead_printscreen

@wesleycho
Copy link
Contributor

That is actually a bug that has been existing for about 2-3 years on the demo page, but no fix yet.

@frfancha
Copy link

Ok but note that in the plunker without the fix (demo in 5180) I can't reproduce this last problem (at least not after 20 tries) (But I see the bug described in 5180 of course)

@deeg
Copy link
Contributor Author

deeg commented Jan 14, 2016

I am planning to fix another bug out there while making the behavior a bit better.

I will take a look at the issue you are describing @frfancha and see if I can't fix that also.

@wesleycho, do you know if there is a ticket for that one?

@wesleycho
Copy link
Contributor

The positioning issue with the typeahead demo is the second mentioned in #1988

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using arrow keys to navigate typeahead response causes page to move when typeahead below the fold
4 participants