-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD E/PR #535] [$250] Chat - In mWeb, text is centered but in Android text is dropping down #52827
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
Comments
Triggered auto assignment to @alexpensify ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Headings are not vertically centered on Android. What is the root cause of that problem?The line height is enlarged on Android to fix overlapping lines. ![]() However, the text is bottom-aligned in ![]() What changes do you think we should make in order to solve the problem?Fine-tune the @Override
public void chooseHeight(CharSequence text, int start, int end, int spanstartv, int lineHeight, Paint.FontMetricsInt fm) {
float leading = mLineHeight - ((-fm.ascent) + fm.descent);
fm.ascent -= (int)Math.ceil(leading / 2.0);
fm.descent += (int)Math.floor(leading / 2.0);
// The top of the first line, and the bottom of the last line, may influence bounds of the
// paragraph, so we match them to the text ascent/descent. It is otherwise desirable to allow
// line boxes to overlap (to allow too large glyphs to be drawn outside them), so we do not
// adjust the top/bottom of interior line-boxes.
if (start == 0) {
fm.top = fm.ascent;
}
if (end == text.length()) {
fm.bottom = fm.descent;
}
} Screenshots
What alternative solutions did you explore? (Optional)N/A |
I didn't get to test this one before going OOO. This week, I'll try to log in to confirm the next steps. |
@alexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
No update |
Job added to Upwork: https://www.upwork.com/jobs/~021863815952930925048 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @alitoshmatov ( |
@alitoshmatov - I was able to replicate the experience. Can you please verify if this proposal will fix the issue? Thanks! |
@alexpensify @alitoshmatov this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@alexpensify, @alitoshmatov Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@QichenZhu Are you suggestion that this should be fixed in |
@alitoshmatov That’s correct. |
@alexpensify, @alitoshmatov Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Weekly Update: Expensify/react-native-live-markdown#535 is still under review |
Weekly update: same as last week |
Weekly Update: No movement in the PR |
Just FYI, I wasn't actively working on this PR because I was hoping that RN 0.76 upgrade would fix this. Unfortunately this is not the case so I'll need to resume working on this PR once I complete my current tasks. |
Oh no, thank you for the update. Keep us posted when you have a better timeline to get to this one. Thanks! |
Weekly Update: Waiting for @tomekzaw to have a free cycle |
Weekly Update: Same |
This comment has been minimized.
This comment has been minimized.
Weekly Update: Same update, but I'm back online. |
Update: I'm working on it, Android already works fine, iOS is almost working but needs some final touches. Latest updates here:
|
Thank you, @tomekzaw, for the update! 🚨 Heads up! I'll be offline until Monday, April 7, 2025, and won’t be actively monitoring this GitHub during that time. If this GitHub requires an urgent update, please reapply the |
This issue has not been updated in over 15 days. @alexpensify, @alitoshmatov eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
@tomekzaw is there any update here? Thanks! |
@alexpensify I've pushed some changes to Expensify/react-native-live-markdown#535 but found out that a proper solution requires some small changes in react-native code. There's also another PR (Expensify/react-native-live-markdown#520) that I'd like to merge prior to this one. |
This issue has not been updated in over 15 days. @alexpensify, @alitoshmatov eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Still waiting on Expensify/react-native-live-markdown#535 |
Uh oh!
There was an error while loading. Please reload this page.
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: V9. 0.64-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
In mWeb, text is centered but in Android text must not drop down.
Actual Result:
In mWeb, text is centered but in Android text is dropping down.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6670752_1732113789398.az_recorder_20241120_200615_compress_1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @alitoshmatovThe text was updated successfully, but these errors were encountered: