Issue 106151 - Text portion containing text field is missing interface XTextField
Summary: Text portion containing text field is missing interface XTextField
Alias: None
Product: Writer
Classification: Application
Component: programming (show other issues)
Version: OOO320m1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: joerg.skottke
QA Contact: issues@sw
Keywords: regression
Depends on:
Reported: 2009-10-21 15:03 UTC by eymux2009
Modified: 2011-02-09 10:51 UTC (History)
3 users (show)

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

See issue description. (8.86 KB, application/vnd.oasis.opendocument.text)
2009-10-21 15:06 UTC, eymux2009
no flags Details
expanded test case (9.03 KB, application/vnd.oasis.opendocument.text)
2009-10-26 09:07 UTC, eymux2009
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description eymux2009 2009-10-21 15:03:07 UTC
In prior versions a text portion (XTextPortion), that contained a text field,
implemented the XTextField interface, too. This interface is now missing.
I'm attaching a Writer document, which reproduces the issue. It contains a
single text field, a bookmark on the text field and a Basic macro
(Module1.Main), which queries the interfaces on the text portions in the
bookmark. On running the macro a message will be printed, whether the XTextField
interface has been found.
I tested this on OOo 3.01 and OOo 3.20m1.
Comment 1 eymux2009 2009-10-21 15:06:43 UTC
Created attachment 65513 [details]
See issue description.
Comment 2 eric.savary 2009-10-21 17:14:19 UTC
Reassigned to JSK
Comment 3 Daniel Benkmann 2009-10-23 14:22:08 UTC
To clarify the test case:
1. Open the attached document testXTextField.odt
2. Execute the macro testXTextField.odt->Standard->Module1->Main

On OOo versions prior to 3.2 you get the message "Interface XTextField found",
on 3.2 the interface isn't found and you get the corresponding message.

This is a pretty major regression and potentially breaks a lot of macros and
extensions that depend on this interface. It should be considered as a blocker
for 3.2.
Comment 4 eymux2009 2009-10-26 09:04:15 UTC
I identified another missing interface. XTextPortion is also no longer
implementing XTextContent.
These seemingly randomly missing interfaces are a major problem. This could
break any code that expects a certain interface to exist. And it can be detected
at runtime only.
I have expanded the test case document to test for the XTextContent interface in
a XTextPortion. An additional message 'interface XTextContent found' on OOo 3.01
and 'interface XTextContent no found' on OOo 3.2 is shown.
Comment 5 eymux2009 2009-10-26 09:07:20 UTC
Created attachment 65605 [details]
expanded test case
Comment 6 cno 2009-11-26 14:43:41 UTC
confirm & set to regression
Comment 7 Mathias_Bauer 2011-02-07 13:02:22 UTC
This was changed by intent.
The old behavior was undocumented and didn't make sense.
Now the text portion has a property named "TextField". And this time it's also
documented. :-)
Comment 8 Mathias_Bauer 2011-02-09 10:51:57 UTC