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 18151 - Allow to set accessible description to Frames and Workspaces.
Summary: Allow to set accessible description to Frames and Workspaces.
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: jrojcek
URL:
Keywords: A11Y
: 17391 17611 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-11-28 15:01 UTC by jrojcek
Modified: 2008-12-23 09:46 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
patch (23.51 KB, patch)
2001-11-28 15:04 UTC, jrojcek 		Details | Diff
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 jrojcek 2001-11-28 15:01:09 UTC 
It is not possible to set accessible description to Frames (Modes) and Workspaces.
Comment 1 jrojcek 2001-11-28 15:04:05 UTC 
Created attachment 3607 [details]
patch
Comment 2 jrojcek 2001-11-28 15:06:00 UTC 
Hi Dafe,
please have a look at attached patch.
Comment 3 David Simonek 2001-11-29 11:48:34 UTC 
Jano, it looks good, great. Only one thing tha came on my mind -
winsys xml files are not validated, so even you specified in DTD that
both bundle and display attributes are REQUIRED, code should be
prepared that it may be broken - bundle and/or display may be missing
or contain incorrect data. Code should survive that.
So please test not only with right xmls, but with "evil" ones too. Thanks.
Comment 4 jrojcek 2001-11-29 15:22:42 UTC 
I have recently committed the patch to release33 branch. 

But I have modified dtds what is (now I know) against versioning
policy for dtds
(http://openide.netbeans.org/versioning-policy.html#2.4). Should I
rollback changes to xml winsys dtds and create new dtds as policy states?
Comment 5 Jesse Glick 2001-11-29 16:33:06 UTC 
IMHO don't worry about creating fresh DTDs. (1) the change is
compatible for existing XML files so they would not be harmed. (2) the
old DTD has never been used in a released version of NB. True it
exists in the release330 branch, but the official DTD on the website
at the time of 3.3.0 release will contain the <description> element.
We should probably only be concerned about making fresh DTDs for cases
where the old one was in wide use beforehand.

We might consider changing the bundled DTD in release330 branch and
making sure that the parser in that branch accepts the <description>
element (and ignores it), so that modules using <description> could
work without errors in 3.3.0, until 3.3.1 is released. I'm not sure if
this is a good idea or not.
Comment 6 jrojcek 2001-11-29 17:00:44 UTC 
OK, marking as fixed.
Comment 7 jrojcek 2001-12-04 13:55:24 UTC 
*** Issue 17391 has been marked as a duplicate of this issue. ***
Comment 8 jrojcek 2001-12-04 13:56:06 UTC 
*** Issue 17611 has been marked as a duplicate of this issue. ***
Comment 9 Marian Mirilovic 2002-01-11 16:00:53 UTC 
verified in [nb331_dev](20020111)
Comment 10 Quality Engineering 2003-07-01 16:51:43 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.