Bug 21586 - Resizing bug on StyledMultilineElement and proposed FIX
Summary: Resizing bug on StyledMultilineElement and proposed FIX
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 7.2.5
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-07-24 17:51 UTC by ianj
Modified: 2016-05-25 00:20 UTC (History)
5 users (show)

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

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:

Description ianj 2014-07-24 17:51:03 UTC
I have found a bug and also have a resolution to a problem with StyledMultilineElement in MonoTouch.Dialog.  Essentially the dialog does not properly allow the dialog to refresh after a Navigator POP action.  When I investigated the code in the Assembly browser I found the problem and the solution uniformly corrects my issue.

It's described in detail here:

Comment 1 Alex Soto [MSFT] 2014-07-31 23:43:40 UTC
Hello Ian

I am trying to reproduce the issue you are having but I've been unable to do it. could you provide a test case so we can verify it?

thanks in advance.

Comment 2 Sebastien Pouliot 2016-05-25 00:20:08 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!