Accessibility/TextAttributes: Difference between revisions

Accessibility/TextAttributes (view source)

Revision as of 17:36, 20 November 2007

96 bytes removed , 20 November 2007

no edit summary

Aaronlev

346

edits

@@ Line 33: / Line 33: @@
 A collection of text attributes (the list of pairs consisted from name and value). All text attributes that apply to the current range are exposed, but in order to conserve the amount of data passed, most text attributes will have reasonable defaults and will not be exposed in the list when they are equal to the default. For example, if font-style is "normal" it will not be exposed in the return value. See the list of text attributes below to find the defaults.
+The following method returns a collection of text attributes that apply to the entire text object:
+  nsIPersistentProperties getDefaultTextAttributes()
+A collection of text attributes (the list of pairs consisted from name and value). All text attributes that apply to the current accessible text object are exposed. Since IA2 does not support default attributes, the IA2 implementation will combine the default attributes into the range attributes before exposing IA2::attributes to the AT.
 = Events =
@@ Line 44: / Line 50: @@
 = Questions =
-== ATK default attribute questions ==
-# Should we support ATK default attributes? IA2 does not have them. We could do it through an object attribute, if we really need it.
 == Unit questions ==
-# The IA2 site does not say what unit color values are exposed as -- it just says use CSS values. However, in CSS colors can be exposed in many different ways. You can use the color name, you can use a 3 digit hex value, a 6 digit hex value, 3 comma-separated unsigned shorts, ....  Is it better just to get 3 comma separated unsigned shorts (R, G, B) so you can determine a name for the color yourself?
+# What units should be used to expose a length, e.g. margin-left. What do ODF editors do?
-# We have a similar problem for anything exposing a length, e.g. margin-left. How do you want the units?
 == Event questions ==
 # It's not clear how to track CSS style changes mapped to text attributes. Possibly some of those changes will lead accessible is recreated. For the most important case, rich text editing, there will be a DOM change.