...where for whatever reason (TODO: investigate) they keep failing at least with
my local Mac OS X 10.7 build at
toolkit.AccessibleFixedText::com::sun:⭐:accessibility::XAccessibleText:
LOG> getCharacterBounds(-1)
LOG> Expected exception
LOG> getCharacterBounds(8)
LOG> Expected exception
LOG> getCharacterBounds(0)
LOG> Text at this place: F
LOG> Character bounds outside component
LOG> Character rect: 1, 3, 6, 11
LOG> Component rect: 0, 22, 100, 12
LOG> getCharacterBounds(1)
LOG> Text at this place: x
LOG> Character bounds outside component
LOG> Character rect: 6, 6, 10, 8
LOG> Component rect: 0, 22, 100, 12
LOG> getCharacterBounds(2)
LOG> Text at this place: e
LOG> Character bounds outside component
LOG> Character rect: 15, 6, 7, 8
LOG> Component rect: 0, 22, 100, 12
LOG> getCharacterBounds(3)
LOG> Text at this place: d
LOG> Character bounds outside component
LOG> Character rect: 22, 3, 7, 11
LOG> Component rect: 0, 22, 100, 12
LOG> getCharacterBounds(4)
LOG> Text at this place: T
LOG> Character bounds outside component
LOG> Character rect: 30, 3, 8, 11
LOG> Component rect: 0, 22, 100, 12
LOG> getCharacterBounds(5)
LOG> Text at this place: e
LOG> Character bounds outside component
LOG> Character rect: 39, 6, 7, 8
LOG> Component rect: 0, 22, 100, 12
LOG> getCharacterBounds(6)
LOG> Text at this place: x
LOG> Character bounds outside component
LOG> Character rect: 45, 6, 10, 8
LOG> Component rect: 0, 22, 100, 12
Change-Id: I690ffc773b53e0f19536605e3cb89280bc98c19a
related, i#87757 and 8bafe38c569afa2e1055eb647cb7ff161ddd1230
which itself is related to ce14342c4292628a641a72d4f63d9c048e030c6a,
These character bounds are backed by what's the glyph bounding box for the ink
used for the glyph. Whitespace has no ink so its an empty Rectangle. Which
brings the awesome RECT_EMPTY into play.
It might be a bit dubious in the first place to back getCharacterBounds with
the glyph bounding box in the first place, rather than maybe the advance width
or some such. But lets assume that decision was intentional.
So, the qa test should accept that a glyph might be of 0 width anyway.
Then, tweak rectangle merging so that we can preserve the correct top-left
position of an empty glyph
So, we can determine the correct character index given the top-left position
of an empty glyph
Change-Id: I5e18460ff7cd90cd27d5eede2aa0a5494c36a5d3
Do not check length of first word for AccessibleStatusBarItem, which
now contains "Words: 0" since ce14342c4292628a641a72d4f63d9c048e030c6a,
but the test stupidly assumes that its text does not contain a space.
