Bug 12312 - OnLine NSUrl documentation is all over the place.
Summary: OnLine NSUrl documentation is all over the place.
Status: CONFIRMED
Alias: None
Product: Documentation
Classification: Xamarin
Component: MonoTouch ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Joel Martinez
URL:
Depends on:
Blocks:
 
Reported: 2013-05-20 17:15 UTC by Joseph Remes
Modified: 2015-11-04 11:08 UTC (History)
3 users (show)

Tags:
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 for Bug 12312 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Comment 8 Miguel de Icaza [MSFT] 2013-05-27 06:29:57 UTC
Jeremie, can you investigate?
Comment 9 Joseph Remes 2013-06-10 13:14:37 UTC
New Info.
MonoTouch.CoreGraphics.CGAffineTransform has the same problem.
Seems to get out of sync at the Rotate method.
Comment 10 Joel Martinez 2015-11-04 11:08:13 UTC
I've confirmed that this issue is still occurring in the latest iteration of the API docs. On first glance, it seems like this might be related to inherited members (which generally in monodoc, are documented on the base type ... a general improvement I hope to make in the future).