-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Toolbar title is moving when swapping fragments #304
Comments
Workaround for this would be to move the |
@mzgreen have you tried the latest support lib, (24.0.0) some users have reported the Jumping around has been fixed. |
Yes, the sample code actually uses 24.0.0. |
It worked for me: |
@nik27 where exactly did you put that? |
Setting null probably instantiates the subTitle TextView so it's laid out On Thu, 14 Jul 2016 at 14:41 mzgreen [email protected] wrote:
|
@chrisjenx |
This seems to only periodically occur in my case. Maybe 80% of the time instead of a font change being applied to my Frustratingly, I'm doing nothing with subtitles at all in my application. |
Maybe I've narrowed it down. It seems when the first toolbar is being rendered, the bug occurs, but if the app is still in memory or I'm going to another fragment, the title rendering works. Closing the app and reopening works correctly, but closing, swiping from recent apps, then reopening causes the bug. |
As for @nik27's suggestion about The |
This happened quite randomly. Upgrading to support lib v24.x wouldn't resolve the issue. I think I'm gonna put the |
@chrisjenx First of all I also have the So I don't have a solution, yet, but wanted to add my findings to this. I will take another look on Monday. Thanks for this nice library, btw. Really makes my life easier! :) |
Wondering if this fixes it #327 |
Yes, it appears to, actually. In addition to no "empty" subtitle showing up anymore, the custom font seems to be applied consistently, now. I was counting on the first part being fixed by this, but have to say that I'm a little bit confused about how this fixes the second one. ;) Although I have to admit that I have troubles reproducing the issues at all with the release version right now. Last week I got the behavior pretty constantly. |
@chrisjenx @Bombo |
This still doesn't work for me. I'm on support |
Could do a custom toolbar. But there is a pull request that might fix this.
…On Thu, 22 Dec 2016, 15:32 mzgreen, ***@***.***> wrote:
This still doesn't work for me. I'm on support 25.1.0.
Everything seems to be ok, but if I start switching between 2 fragments
back and forth then after couple of trials toolbar stays aligned to top
(invisible subtitle?) with Roboto instead of custom font.
Is there any known workaround? Maybe wrapping TextView inside Toolbar
would help?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABHRsQvkfioQBaj3FZlF1EKNaOOvPwHYks5rKooSgaJpZM4JG067>
.
|
What do you mean by custom Toolbar? Put TextView inside and not use toolbar's title property or completely custom view instead on toolbar? |
Correct
…On Thu, 22 Dec 2016, 16:16 mzgreen, ***@***.***> wrote:
What do you mean by custom Toolbar? Put TextView inside and not use
toolbar's title property or completely custom view instead on toolbar?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#304 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABHRsb3Xrth1-WWaiygcAhoIxQipNh_sks5rKpQjgaJpZM4JG067>
.
|
This probably closes chrisjenx#280, chrisjenx#304 and chrisjenx#363
Hi!
I have one activity and two fragments. Each fragment has it's own
Toolbar
with different title. When I swap fragments (usingtransaction.replace
) then the title is moving/jumping. In 2.1.0 it's a little better. Movement is a lot less visible but it's still there.Here is a sample project that reproduces this issue: https://drive.google.com/open?id=0B4aF0Bxe-ecnRjBCaEdIMzMxYVU
It's not using any custom fonts, wrapping
Context
inattachBaseContext
is enough to reproduce this issue.The text was updated successfully, but these errors were encountered: