Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312355

Summary:	[Accessibility] Can't detect changes in alignment or justification with current API
Product:	[Eclipse Project] Platform	Reporter:	Scott Kovatch <skovatch>
Component:	SWT	Assignee:	Scott Kovatch <skovatch>
Status:	CLOSED WONTFIX	QA Contact:	Carolyn MacLeod <carolynmacleod4>
Severity:	normal
Priority:	P3	CC:	eclipse.felipe, Silenio_Quarti
Version:	3.6
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:	stalebug

Description Scott Kovatch

2010-05-10 19:30:35 EDT

AccessibleAttributeListener's getAttributes method returns a collection of metrics about a text object, but it doesn't have enough granularity to return information about a run of text. If a text object changes alignment or justification there's no way to query whether the text at the cursor is left, right, or center aligned.

To see this, run Snippet213 on 3.6 Cocoa and turn on VoiceOver. Although the alignment changes from paragraph to paragraph, we have no way of reporting the alignment to the user. Instead, we return the default alignment for the StyledText, which is SWT.LEFT.

Comment 1 Scott Kovatch

2010-05-10 19:35:26 EDT

There are a couple of ways to handle this:

- extend TextStyle to have an alignment field
- change AccessibleAttributeEvent so it can take an offset/line number/something as an input field. AccessibleAttributeListener.getAttributes() then needs to set the line/offset for which we are interested.
- ???

Comment 2 Eclipse Webmaster

2019-09-06 16:12:06 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 3 Eclipse Genie

2021-10-27 03:00:03 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.