8000 Customising overflow position for Text Widget · Issue #76943 · flutter/flutter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Customising overflow position for Text Widget #76943

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.

Sign up for GitHub

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

Jump to bottom
Open
Anushi1998 opened this issue Feb 28, 2021 · 9 comments
Open

Customising overflow position for Text Widget #76943

Anushi1998 opened this issue Feb 28, 2021 · 9 comments
Labels
a: typography Text rendering, possibly libtxt c: new feature Nothing broken; request for a new capability c: proposal A detailed proposal for a change to Flutter customer: money (g3) engine flutter/engine repository. See also e: labels. framework flutter/packages/flutter repository. See also f: labels. P1 High-priority issues at the top of the work list team-engine Owned by Engine team triaged-engine Triaged by Engine team

Comments

@Anushi1998
Copy link
Anushi1998 commented Feb 28, 2021 •
edited
Loading

Currently, Text widget supports only limited options for painting overflowed text.

Can we customize the overflow options to support custom truncation positions eg. before @ for emails? For reference, iOS SDK also supports three different types of modes.

Other open issues related to this -

Internal bug - b/180975303
@pedromassangocode pedromassangocode added the in triage Presently being triaged by the triage team label Mar 1, 2021
@pedromassangocode
Copy link

Hi @Anushi1998
The iOS types are covered in #45336.

Can we customize the overflow options to support custom truncation positions eg. before @ for emails?

Can you please elaborate how this will work for text with more than one @? assuming that the text is not a Email.
Thank you

@pedromassangocode pedromassangocode added the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Mar 1, 2021
@Anushi1998
Copy link
Author

With our current requirements of feature, it is certain that there is only one @. Also, I would assume flutter to delegate choosing ellipsis place to the invoker, so cases of multiple @ can be handled gracefully.

@no-response no-response bot removed the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Mar 1, 2021
@pedromassangocode pedromassangocode added a: typography Text rendering, possibly libtxt framework flutter/packages/flutter repository. See also f: labels. passed first triage c: proposal A detailed proposal for a change to Flutter c: new feature Nothing broken; request for a new capability and removed in triage Presently being triaged by the triage team labels Mar 1, 2021
@goderbauer goderbauer added the engine flutter/engine repository. See also e: labels. label Mar 4, 2021
@jiahaog jiahaog added customer: money (g3) P1 High-priority issues at the top of the work list labels Mar 8, 2021
@pedromassango pedromassango changed the title Customising overflow for Text Widget Customising overflow position for Text Widget Apr 26, 2021
@zanderso zanderso added P3 Issues that are less important to the Flutter project and removed P1 High-priority issues at the top of the work list labels May 26, 2021
@chingjun
Copy link
Contributor
chingjun commented Jun 9, 2021

Changing the priority to match the priority of the internal bug b/180975303.

When this bug is triaged again in the future, can you also comment in, and change the priority of the internal bug? Thanks.

@chingjun chingjun added P1 High-priority issues at the top of the work list and removed P3 Issues that are less important to the Flutter project labels Jun 9, 2021
@YeungKC YeungKC mentioned this issue Jun 14, 2021
Open
@flutter-triage-bot flutter-triage-bot bot added multiteam-retriage-candidate team-engine Owned by Engine team triaged-engine Triaged by Engine team labels Jul 8, 2023
@flutter-triage-bot flutter-triage-bot bot removed the triaged-engine Triaged by Engine team label Dec 26, 2023
@flutter-triage-bot
Copy link

This issue is marked P1 but has had no recent status updates.

The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

@jonahwilliams jonahwilliams added the triaged-engine Triaged by Engine team label Jan 22, 2024
@LongCatIsLooong
Copy link
Contributor
8000 LongCatIsLooong commented Jun 11, 2024

Duplicate of #45336

@LongCatIsLooong LongCatIsLooong marked this as a duplicate of #45336 Jun 11, 2024
@LongCatIsLooong LongCatIsLooong closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
@LongCatIsLooong LongCatIsLooong added the r: duplicate Issue is closed as a duplicate of an existing issue label Jun 11, 2024
@github-actions GitHub Actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 25, 2024
@gnprice
Copy link
Member
gnprice commented Jun 25, 2024

I think this is distinct from #45336.

That issue asks for a standard set of three options: ellipsis at start, middle, or end. This one asks to go beyond that to more arbitrary flexibility:

custom truncation positions eg. before @ for emails

Not that I personally have an idea for a good API for providing that feature, though. Given the level of activity on this issue, it might just hang out at P2 or P3 indefinitely, and that's fine.

@gnprice gnprice reopened this Jun 25, 2024
@flutter flutter unlocked this conversation Jun 25, 2024
@gnprice gnprice removed the r: duplicate Issue is closed as a duplicate of an existing issue label Jun 25, 2024
@flutter-triage-bot flutter-triage-bot bot removed the triaged-engine Triaged by Engine team label Oct 29, 2024
@flutter-triage-bot
Copy link

This issue is marked P1 but has had no recent status updates.

The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

@jonahwilliams jonahwilliams added the triaged-engine Triaged by Engine team label Nov 4, 2024
@flutter-triage-bot
Copy link

This issue is marked P1 but has had no recent status updates.

The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

@flutter-triage-bot flutter-triage-bot bot removed the triaged-engine Triaged by Engine team label Mar 10, 2025
@jonahwilliams jonahwilliams added the triaged-engine Triaged by Engine team label Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
a: typography Text rendering, possibly libtxt c: new feature Nothing broken; request for a new capability c: proposal A detailed proposal for a change to Flutter customer: money (g3) engine flutter/engine repository. See also e: labels. framework flutter/packages/flutter repository. See also f: labels. P1 High-priority issues at the top of the work list team-engine Owned by Engine team triaged-engine Triaged by Engine team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@gnprice @Hixie @goderbauer @chingjun @zanderso @jiahaog @jonahwilliams @Anushi1998 @LongCatIsLooong @pedromassangocode
0