-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
input placeholder covers value when using OnPush detection strategy #3005
Comments
I have the exactly same issue on my project that the placeholder value overlap with the input value. |
I'm seeing this manifest in browser-populated fields - specifically userName and password fields populated by Chrome et. al. My normal temporary hack of
fails for this case, however. Edit: It's a bit more of an edge case than I realised. It only happens if the page is not currently focused - presumably related to the fact that the change listener doesn't fire either, in the same case. To reproduce I have to have the cursor in the address bar and hit enter. The page reloads the label is covering the auto-populated password field. Using keyboard shortcuts to refresh while focused on the console pane causes it also. The placeholder jumps into the correct place as soon as the page body gets focus. |
maybe related to #2663 says it's fixed but i'm still having this issue using select in combination with reactive forms/OnPush change detection.( Angular 4.0.0, material 2.0.0.beta2) |
for me this all works as expected now.(beta 3) Good work! |
@mjolk , can you share how did was it fixed for you? i still can't have it working. |
@mjolk What you do for OnPush work with input placeholder, i have last version (2.0.0-beta.3) and the problem persist. |
Still an issue for me as well. I've worked around it with:
In ngOnInit / ngAfterViewInit. |
@ggranum solution worked out for me, just that I've put it in the subscribe where the actual data is rendered. |
i use markForCheck() as well, not specifically for this reason , but it apparently was the reason it worked( before in the exact same setup it didn't). It is logical( to me in my use case) the render does not happen without marking the component dirty( in a situation where there is new data from a subscription) manually so i did not think it was a bug/it was fixed |
I came to report the same issue - glad I searched before creating a new one. Here's my plunker for good measure |
Still seeing this issue: #4814 |
I am still facing issue even with timeout hack. Is there anything else can be done to fix? (OnPush + ngModel) |
This problem back in beta.10. |
@MaickelHubner can you reproduce it and open a new issue? |
This problem is back in beta 12, any solution? |
Would be great to have a solution because as it is now its not possible to use fields(( ... It was working fine in beta 11 .. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
I know there were couple of these before, but it seems to be happening again https://gist.run/?id=d815c9d4e98685976793d074fcc89c23
cc @kara @mmalerba maybe?
The text was updated successfully, but these errors were encountered: