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 36840

Summary: a11y: focus has been lost in Source Editor view.
Product: utilities Reporter: tanya <tanya>
Component: PropertiesAssignee: Jan Stola <jstola>
Status: RESOLVED FIXED    
Severity: blocker CC: bnv, ccv, juhrik, mbudris, petersl, tanya, vgorr
Priority: P3 Keywords: A11Y, FOCUS
Version: -S1S-   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Bug Depends on: 40507    
Bug Blocks:    

Description tanya 2003-10-27 09:54:13 UTC
Product Version:  Sun ONE Studio 5  Standard
Edition (Build 030904)
IDE Versioning:   IDE/1 spec=3.42.2 impl=030904
Operating System: SunOs version 5.8 running on sparc
Java:             1.4.1_05


    To reproduce the bug:
    
1. Having focus in the Explorer[Filesystem],
   create Properties File through
File/New/Other/Properties File.
   
   Source editor view appears, but focus is on the
node created.
   
ISSUE 1:  Focus should be in Source Editor view.
Ctrl-3 highlihgts
          Source Editor[<Properties File> node *]
view, but focus
          remains in Filesystems view.
   
ISSUE 2: There are no properties in the table yet,
but 'Remove Property'
         button is enabled.
                  
2. Fource focus into Source Editor view using
mouse and create New Property.
3. Press Space in Key or Value table cell to start
editing.

ISSUE 3: You can`t move focus to the next
component using Ctrl-Tab.
Comment 1 Marian Petras 2004-02-26 08:01:19 UTC
I am able to reproduce all the three mentioned issues on a PC+Linux
platform with a NetBeans 3.6 beta. They will not be fixed in NetBeans 3.6.

Issue #1 is caused by bug #40507 ("Activating a TopComponent does not
move focus to its focus cycle").
Comment 2 Jan Stola 2004-07-21 10:45:09 UTC
issue 1: fixed - the focus is moved into the editor by now.

issue 2: fixed - Remove Property button is disabled when no
  property is selected (for example when there is no property).

issue 3: this seems to be a misunderstanding. It works correctly.
  The only "problem" is that (on some look and feels?) Ctrl+Tab
  moves focus on the scrollbar of the textarea. After that just
  simple Tab must be used to move focus to the next component.