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 135350 - A11Y: Components not reachable with tab traversal in "jdbc:mysql://jbrave-pc1.sfbay.sun.com/travel [travel on Default schema]" dialog
Summary: A11Y: Components not reachable with tab traversal in "jdbc:mysql://jbrave-pc1...
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: John Baker
URL:
Keywords: A11Y
: 108785 (view as bug list)
Depends on:
Blocks: 152776
  Show dependency tree
 
Reported: 2008-05-19 16:55 UTC by Roman Mostyka
Modified: 2016-06-17 08:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2008-05-19 16:55:34 UTC 
Components not reachable with tab traversal :
  Class: org.netbeans.api.visual.widget.SceneComponent {  |  } 
  Class: org.netbeans.modules.db.sql.visualeditor.querybuilder.QueryBuilderInputTable {  Query Table |  Tabular
representation of the query } 
  Class: org.netbeans.modules.db.sql.visualeditor.querybuilder.QueryBuilderSqlTextArea {  Query Text |  Textual
representation of the query } 
  Class: org.netbeans.modules.db.sql.visualeditor.querybuilder.QueryBuilderTable {  |  }
Comment 1 Roman Mostyka 2008-11-08 13:16:44 UTC 
According to http://wiki.netbeans.org/BugPriorityGuidelines it can be P1.
Comment 2 John Baker 2008-11-09 00:41:49 UTC 
this is the same as the other issue

Why file this now ???

*** This issue has been marked as a duplicate of 108785 ***
Comment 3 Roman Mostyka 2008-11-09 18:12:30 UTC 
I think that this issue describes more exactly which parts of Query Editor dialog aren't reachable by keyboard.
If if you look at creation date, you'll see that this issue was created on May 19 2008. But priority rules for A11Y
issues were changed from that time. Now I just went through the list of issues and found this issue and updated it,
that's all.
Comment 4 Roman Mostyka 2008-11-09 18:12:43 UTC 
*** Issue 108785 has been marked as a duplicate of this issue. ***
Comment 5 Roman Mostyka 2008-11-10 13:13:17 UTC 
Since Visual Web module is in maintenance mode now, I don't think that this issue is showstopper.
It is P1 according to new rules, but I think we can fix this issue in Patch 1.
Comment 6 Petr Blaha 2008-11-10 17:23:03 UTC 
Downgrade to P2 since the issue isn't stopper in 6.5.
Comment 7 Roman Mostyka 2008-11-10 17:30:29 UTC 
Petr, is there any keyword or something like this to mark issue as NOT showstopper.
According to Bug Priority Guidelines this issue is P1 and downgrading is not corresponding with Guidelines.
Or we don't have any mechanism for such cases?
Comment 8 Petr Blaha 2008-11-18 13:07:55 UTC 
Move visualsqleditor subcomponents below visualweb
Comment 9 pgebauer 2008-11-24 09:31:10 UTC 
The issue didn't pass the nomination process by nomination cut-off date. It has been marked as 65fixes2-candidate.
Comment 10 Peter Zavadsky 2008-12-16 20:25:16 UTC 
I checked the code. The implementation is not architected well, and it seems there would be needed to add an
implementation of specific FocusTraversalPolicy, if not more, it would need to take more time to find out exactly (there
might be some issue with that, since it was not done by the owners before).

Currently there is no manpower assigned to that, also the functionality is moving away from the user attention.
Would it be OK to downgrade to P3?
Comment 11 Roman Mostyka 2008-12-17 09:41:51 UTC 
I don't have any objections since visualweb module is in maintenance mode. But according to
http://wiki.netbeans.org/BugPriorityGuidelines it should be even P1. So probably we should have confirmation from higher
level.
Comment 12 Peter Zavadsky 2008-12-23 21:22:51 UTC 
Could you, please, get that confirmation? Thanks.
Comment 13 Roman Mostyka 2008-12-24 09:32:03 UTC 
Petr, please look at desc11 and desc12 and confirm please if we can decrease priority.
Comment 14 Peter Zavadsky 2009-01-05 19:24:04 UTC 
Roman, what do you mean by desc11 and desc12?
Comment 15 pgebauer 2009-01-14 09:50:04 UTC 
The issue hasn't passed the nomination process for 65patch2 by cut-off date. It has been moved to 65patch3.
Comment 16 pgebauer 2009-02-01 22:35:02 UTC 
I'm not sure why the issue has been reopened but it shouldn't be reopened base on unsuccessful verification in 65patch2. The port from the trunk to the 
release65_fixes branch isn't straight forward. If everything is OK in the trunk (I think so, because the issue has been verified already), the status should be 
get back.

kaa, could you please check it?
Comment 17 pgebauer 2009-04-08 14:02:24 UTC 
The status whiteboard "65fixes4-candidate" has been removed.
At this time our proactive patches for the NetBeans 6.5.x IDE have concluded.

If you own a Sun service plan contract for NetBeans, you may wish to contact
Sun Service http://www.sun.com/contact/support.jsp to request a fix via the
product defect escalation process.

For more information on purchasing a Sun service plan contract for NetBeans,
refer to the service plan item "Sun Software Service Plans (S3P) for Developers"
in the Sun Service table found on our NetBeans Support Resources
page http://www.netbeans.org/kb/support.html
Comment 18 Jiri Kovalsky 2016-06-17 08:36:02 UTC 
VisualWeb support is no longer available in the NetBeans IDE so we are not going to fix this problem. Resolving accordingly.

[1] http://wiki.netbeans.org/NetBeansArchivedFeatures#Visual_Web_module