Issue 50478 - Handle embedded object linked data correctly.
Summary: Handle embedded object linked data correctly.
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-06-08 11:31 UTC by mikhail.voytenko
Modified: 2017-05-20 11:27 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description mikhail.voytenko 2005-06-08 11:31:07 UTC
This is a successor of the issue 49370.

Design and implement the missing functionality in the Container so that it can
be used in the .uno:CloseFrame handling in embedded object implementation. I am
still not sure how should the changes in the linked by embedded object data be
handled. In the original bug the document was opened readonly, in this case the
linked data should not be stored by default probably. But if it is opened for
editing, the data probably should be stored quietly. The container still has a
possibility to influence the process by providing of the own interceptor
Comment 1 mikhail.voytenko 2005-06-08 11:37:45 UTC
Ups, sorry.
In the previous posting please read "...the missing functionality in the
Controller..." instead of "...the missing functionality in the Container...".
Comment 2 Marcus 2017-05-20 11:27:53 UTC
Reset assigne to the default "".