Issue 100044 - Testtool: Additional characters retrieved when reading content of listbox
Summary: Testtool: Additional characters retrieved when reading content of listbox
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOO310m4
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: joerg.skottke
QA Contact: issues@framework
URL:
Keywords: regression
Depends on: 100057
Blocks: 95768
  Show dependency tree
 
Reported: 2009-03-09 12:46 UTC by joerg.skottke
Modified: 2009-03-17 20:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Resultfile (12.55 KB, text/plain)
2009-03-09 12:48 UTC, joerg.skottke
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2009-03-09 12:46:38 UTC
Automated test: framework/optional/f_configuration.bas

On MacOSX we get at least one additional character from the listbox of the
"Manage User Interface Languages" dialog.
Comment 1 joerg.skottke 2009-03-09 12:48:12 UTC
Created attachment 60825 [details]
Resultfile
Comment 2 joerg.skottke 2009-03-09 12:49:01 UTC
Fix typo
Comment 3 joerg.skottke 2009-03-09 12:59:13 UTC
Workaround for OOO310 is done in the test itself (b_basic_dialog_i18n.bas),
tracked in issue 100045
Comment 4 joerg.skottke 2009-03-09 13:19:16 UTC
Please note: The Testtool does *not* display those characters, use MacOSX with
font Courier to see.
Comment 5 joerg.skottke 2009-03-09 13:22:41 UTC
Note for myself: m3 bad, m4 bad, m1 is good.
Comment 6 joerg.skottke 2009-03-09 13:28:05 UTC
The problem was introduced with the OOO310m2 build

Reassigning to AB.
Comment 7 joerg.skottke 2009-03-09 13:34:30 UTC
Note: I'm going to ditch the workaround announced above in favor of a real fix.
Comment 8 joerg.skottke 2009-03-09 14:48:36 UTC
Setting keyword accessibility (you cannot select a language in any of the
language listboxes using the first character).

All platforms are affected
Comment 9 ab 2009-03-09 14:53:35 UTC
First evaluation shows that this cannot be a Basic problem as
there were no changes at all in Basic from OOO310 m1 to m3.
I will check now what else could have caused the problem.

STARTED
Comment 10 joerg.skottke 2009-03-09 15:03:07 UTC
Corrected Version (was DEV300m4)
Comment 11 hdu@apache.org 2009-03-09 15:18:54 UTC
@ab: issue 85360 introduced the bidi-embedding markers for problematic strings...
Comment 12 ab 2009-03-09 16:02:07 UTC
ab->jsk: According to hdu these bidi markers are part of the strings
intentionally. There's nothing Basic can do about this. This will have
to be fixed in the automated test code as the reference strings really
*are* different.

The first character key problem should be addressed in another issue.
According to hdu this issue should be fixed by er.
Comment 13 joerg.skottke 2009-03-10 12:40:00 UTC
Assigning to GH for fixing in office code.
Comment 14 gregor.hartmann 2009-03-10 13:41:00 UTC
now removing BiDi markers
Comment 15 joerg.skottke 2009-03-10 13:53:04 UTC
Use f_basic_dialog_i18n.bas to check the .getText()/.getSelText() methods and
NewSortingAlgorithmForJapanese.bas to test the .select() method.

Note that GH's library only handles .get*(), HDU's fix (hopefully) also covers
the .select() method.
Comment 16 philipp.lohmann 2009-03-10 16:41:22 UTC
please verify in CWS ooo31gsl4
Comment 17 philipp.lohmann 2009-03-10 16:44:51 UTC
removing accessibility keyword (that's issue 100057). Technically this is not
even a regression, just the Strings were changed in the application but not in
the testtool. However these daft formatting characters are more than a little
bit unwieldy, so it makes sense to filter them out.
Comment 18 joerg.skottke 2009-03-16 13:56:44 UTC
Looks good in Linux and Solaris, setting verified.
Comment 19 joerg.skottke 2009-03-17 20:31:20 UTC
Good in m6 Linux/Windows, closing