This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 270446

Summary: Sharing desktop with WebEx disables context menus, obliterates text line numbers and prevents breakpoint setting
Product: ide Reporter: nikitaxik
Component: UIAssignee: issues@ide <issues>
Status: NEW ---    
Severity: normal    
Priority: P3    
Version: 8.2   
Hardware: PC   
OS: Windows 7   
Issue Type: DEFECT Exception Reporter:
Attachments: Image of messed up file view
IDE log for aditional information

Description nikitaxik 2017-04-20 18:13:39 UTC
Created attachment 164146 [details]
Image of messed up file view

The problem has been consistently observed in NetBeans IDE 8.1, 8.2 and in NetBeans platform applications based on these releases.

When IDE is used in a WebEx session with shared screen, editors of files get disrupted.  Segment of editor windows containing line numbers disappears along with the ability to enable/disable breakpoints.  Context menus in editor windows stop working and some editor navigation features stop functioning.

Closing and opening the file in the editor window temporarily masks the problem for that particular file, but not for others.

If you cannot reproduce it, share the screen in webex and then resize the netbeans window.  Will happen every time.

It is a cosmetic annoyance, but a big one.  Lots of meetings use webex style desktop sharing and these kinds of problems reduce the sense of professionalism and quality of the UI, which is unfortunate.  We have made a decision to use NetBeans platform as basis for a number of our applications, but are very concerned that the customers will view the uis as amateur with these kind of problems.  I already heard people say that "Eclipse does not have this problem, why don't you use it???"  I do not want to have to respond to these questions.
Comment 1 nikitaxik 2017-04-20 18:23:13 UTC
Created attachment 164147 [details]
IDE log for aditional information

Adding a log file from the session which manifested the described problem.
Comment 2 nikitaxik 2017-04-20 18:31:19 UTC
It appears to be related to the Bug 256104 which was reported 2 years ago already, but looks like nobody really looked at it as it is still showing NEW. Would be really nice to have that resolved someday.
Comment 3 nikitaxik 2017-04-20 18:33:35 UTC
Also related to Bug 217787 which tracks back many years.