Bug 36216 - NSTextView not implementing INSTextFinderClient correctly
Summary: NSTextView not implementing INSTextFinderClient correctly
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: mmp ()
Version: Master
Hardware: PC Mac OS
: Normal normal
Target Milestone: 2.8.0 (C7)
Assignee: Chris Hamons
Depends on:
Reported: 2015-11-24 15:21 UTC by Chris Hamons
Modified: 2016-05-20 17:43 UTC (History)
2 users (show)

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

Example + Work around (349.84 KB, application/zip)
2015-11-24 15:27 UTC, Chris Hamons

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 Chris Hamons 2015-11-24 15:21:02 UTC
This making using NSTextFinder difficult.
Comment 1 Chris Hamons 2015-11-24 15:27:04 UTC
Created attachment 13978 [details]
Example + Work around
Comment 2 Chris Hamons 2015-12-04 19:22:10 UTC
* d2738f5 - Fix NSTextView to correctly implement NSTextFinderClient and convince tests that is ok (2 days ago)<Chris Hamons>
Comment 3 Rajneesh Kumar 2016-05-20 17:43:55 UTC
I have checked this issue with the following build from C7:


Now I observed that "_finder.Client = _textView;" is working properly.

Screencast: http://www.screencast.com/t/BHvROZdHb

This this issue has been fixed, hence I am closing this issue.