Bug 13885 - Clicking the chevron in the Solution explorer doesn't expand the node
Summary: Clicking the chevron in the Solution explorer doesn't expand the node
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.12
Hardware: Macintosh Windows
: --- normal
Target Milestone: master
Assignee: Cody Russell
URL:
Depends on:
Blocks:
 
Reported: 2013-08-09 09:24 UTC by Neal
Modified: 2015-04-21 07:43 UTC (History)
2 users (show)

Tags: gtk
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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Neal 2013-08-09 09:24:28 UTC
This is a bug from forever ago and it has returned!  It's been find until about 4.0.11 and now it's back, when trying to expand a folder in the solution explorer, clicking the black arrow/chevron does NOT expand it.  I have to use right/left arrows.  I've tried focusing back to the editor then to the solution explorer, the problem remains.
Comment 1 Mikayla Hutchinson [MSFT] 2013-08-09 12:51:02 UTC
Is this Windows or Mac? If Mac, what's the Mono version information in the About dialog? Id there any way to reproduce this?
Comment 2 Neal 2013-08-09 13:29:07 UTC
Mac - 3.2.1 (alpha channel), now I'm on the beta channel today and so far so good.
Comment 3 Mikayla Hutchinson [MSFT] 2013-08-09 13:41:42 UTC
Yes, even back when this was happening to most users several times a day, it took months to find a set of reproduction steps that would allow us to debug it. It has to do with how the UI toolkit treated mouse enter/leave events from MacOS in different focus states. If it does happen again, please note what you were doing immediately beforehand - what you clicked, what previously had focus. etc.
Comment 4 Neal 2013-08-26 22:46:32 UTC
This happened again, it was right after doing an update from SVN
Comment 5 Chris Howie 2013-11-19 17:31:59 UTC
Some observations about this bug, as I am affected:

It happens on Debian Linux too, not just Mac.  It's been happening in the 4.x releases for months.

Once it gets stuck, it's stuck for a while.  It affects *all treeviews* in MD, that I can tell.  If clicks stop working in the Solution pad, they stop working in the Unit Test pad too, for example.  This hints that the bug is in something common between the two.  (From IRC: 17:25 <@jeff> SerajewelKS, a lot of those pads use the same subclass of TreeView (which is the whole NodeBuilderExtension stuff in MD))

The issue seems to occur most frequently after interacting with some pop-up dialog, for example after editing project options or references.  The issue will go away similarly.  The issue will neither come nor go reliably, however.  When I'm trying to reproduce it, I usually can't get it to happen.

It's important to note that this does not affect expand/collapse keyboard functionality; you can click a row in a treeview and use the + or - key to expand or collapse it, respectively, even when clicking the chevron does not work.  This has been a viable workaround for me, and is a considerably nicer workaround than "restart MD" (which I had been doing).

It seems like some mouse event handler is marking the event as consumed when it should not, though this is just a hunch based on no actual knowledge of the MD codebase.