Bug 33454 - LineBreakMode.TailTruncation could be less agressive in edge cases
Summary: LineBreakMode.TailTruncation could be less agressive in edge cases
Status: RESOLVED INVALID
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.3
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-08-28 06:15 UTC by Michiel van Vlaardingen
Modified: 2015-09-15 06:11 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Example of agressive tail truncation (77.12 KB, image/png)
2015-08-28 06:15 UTC, Michiel van Vlaardingen
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Michiel van Vlaardingen 2015-08-28 06:15:22 UTC
Created attachment 12672 [details]
Example of agressive tail truncation

As can be seen in the screenshot, this label in the top right is tail truncated.  However  the truncation removed the last two characters from the string  only to add the three dots.    the  original  "es" would have taken less space than the "..." so it would have been slightly nicer if the original text remained in this edge case.
Comment 2 Abhishek 2015-09-10 10:15:04 UTC
I have tried this issue but unable to reproduce this issue at my end.

Could you please provide me sample along with the bug so that I can reproduce this issue at my end. Also It would be great if you can provide the IDE log,Device Log and Environment Info.

IDE log via Help->Open log directory.
Environment Info via Xamarin Studio->About Xamarin Studio->details.

Environment Info:

=== Xamarin Studio ===

Version 5.9.6 (build 26)
Installation UUID: 93e693b0-b53d-40f4-b29c-b61ff5cbe892
Runtime:
    Mono 4.0.4 ((detached/5ab4c0d)
    GTK+ 2.24.23 (Raleigh theme)

    Package version: 400040001

=== Xamarin.Android ===

Version: 5.1.6.7 (Enterprise Edition)
Android SDK: /Users/xamarin23/Desktop/android-sdk-macosx
    Supported Android versions:
        2.3    (API level 10)
        4.0.3  (API level 15)
        4.1    (API level 16)
        4.2    (API level 17)
        4.3    (API level 18)
        4.4    (API level 19)
        4.4.87 (API level 20)
        5.0    (API level 21)
        5.1    (API level 22)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Apple Developer Tools ===

Xcode 6.3 (7569)
Build 6D570

=== Xamarin.iOS ===

Version: 8.10.5.26 (Enterprise Edition)
Hash: 6757279
Branch: master
Build date: 2015-08-24 15:04:27-0400

=== Xamarin.Mac ===

Version: 2.0.2.111 (Enterprise Edition)

=== Build Information ===

Release ID: 509060026
Git revision: 031075e25277828f9e74a37906e46818286ec615
Build date: 2015-09-03 15:03:44-04
Xamarin addins: 04612007b3d767c051c04c81df1d5bf03b6d7946

=== Operating System ===

Mac OS X 10.10.0
Darwin 800BC.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 3 Michiel van Vlaardingen 2015-09-15 06:11:31 UTC
No need, the actual measurements in pixels where a bit different from what I expected. So it was not a bug/issue.