Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Sometimes the MD main window behaves very strangely. The window decoration indicates that it has input focus, but GTK's state does not reflect this:
* the text editor renders the selection grey (unfocused) instead of blue (focused)
* the text editor does not render the caret
* all the items in the main menu is disabled menu is disabled, which likely indicates that gtk_window_has_toplevel_focus property is returning false for the main window
This can be worked around by focusing another app, then focusing MD again. Clicking on the window decoration does NOT work.
*** Bug 5513 has been marked as a duplicate of this bug. ***
I am guessing this is very rare?
Basically GDK listens for the windowDidBecomeKey and windowDidResignKey notifications to update the current focus window. You would expect that when the window decoration indicates input focus, GDK has received and processed the notification. Of course, it is still possible that something else caused GDK/GTK+ to think that the window no longer has focus.
Do you have any indication under which circumstances this behavior is triggered?
I don't know of any repro cases. It may have been fixed by other patches. We can leave this bug in a NEEDINFO state until we get another report with the latest GTK+ builds.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.