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 38561 - Need to document some of what should be done with hyperlinks and keyboarding in the IDE
Summary: Need to document some of what should be done with hyperlinks and keyboarding ...
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@ide
Depends on:
Reported: 2004-01-08 21:14 UTC by David-john Burrowes
Modified: 2013-09-04 13:45 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description David-john Burrowes 2004-01-08 21:14:25 UTC
We need to document what should be done with
respect to keyboardability of hyperlinks within
the IDE, since we have these in various contexts
(e.g. the welcome screen).

Below is an email I sent to other HIE's outlining
the problem.  I think the right answer is #1.


Question: what key(s) should activate the hyperlinks?

Precedents: JLF uses space to activate things. 
Web browsers use Enter to activate things and
space to scroll the page.  Some other IDE's honor
the web page idioms for hyperlinks and for
web-page-like parts of the interface.

There are three "obvious" design possibilities:
1) Enter activates hyperlinks, Space activates
other controls.
   Pro: Preserves space for scrolling web-page
things, and enter for default controls
   Con: Forces users to figure out what kind of
component has focus
2) Both enter and space activate hyperlinks, space
activates other controls
   Pro: Allows users to use whatever seems right
for hyperlinks
   Con: blocks space as a scrolling command in
web-page like things.
      Also, doesn't aid the user to figure out
what the (complex) keyboard rules are.
3) Space is used to activate everything (enter
isn't used)
   Pro: Simple and consistent
   Con: Abandons consistency with web page navigation.

I'm inclined towards #1, though #3 has a lot of
appeal (I'm concerned #3 will get in the way
if/when we get more web-page like interface stuff
in the IDE).

Thoughts?  To me, this seems like a "no win"
scenario... we've got two conflicting keyboard
navigation schemes, so there is no way to
absolutely bridge them.  I do'nt know enough about
keyboard users to have a sense of what their
preference would be.
Comment 1 Jiri Mzourek 2004-03-12 15:41:30 UTC
Target milestone updated. 
Comment 2 David Simonek 2006-08-08 18:47:15 UTC
Passing to jdinga.
Comment 3 Jindrich Dinga 2006-08-09 12:41:02 UTC
Reassigning to Jano.
Comment 4 jrojcek 2007-07-19 14:32:17 UTC
Changing to TASK so that it doesn't mix with other defects. The styleguide has not been updated for quite some time. When we get back to it, we should 
document also this issue.