Bug 116435 - XML Form Document: Impossible to rename default-value "instanceData"
Summary: XML Form Document: Impossible to rename default-value "instanceData"
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: preBibisect, regression
Depends on:
Blocks:
 
Reported: 2018-03-16 19:21 UTC by Robert Großkopf
Modified: 2023-03-19 06:41 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2018-03-16 19:21:08 UTC
Open LO.
File > New > XML Form Document
On the right you could see the Data Navigator. If not switch to the bottom of the window, 4th button from the left.
Data Navigator shows "Instance 1" and there "instanceData".
Mark "instanceData" and edit the element (right mousclick > Edit Element)
Change the name, for example, to "Data".
Close the dialog.
No changing has been made.
Add a element with default "newElement".
Change the name, for example, to "New".
Close the dialog.
Element has been renamed.

Renaming works here on all elements, except the root-element "instanceData".

There is one way rename the root-element out of the box:
create a xml-file with the following content
-------------
<?xml version="1.0" encoding="UTF-8"?>
<Main>
</Main>
-------------
Go to Instances (right down on the Data Navigator) > Edit. Browse to the file, click "OK", save the form and reopen it. "instanceData" has been removed by "Main".

All these tested with LO 6.0.2.1 and also the oldest here installed version LO 3.6.7., OpenSUSE 42.3 64bit rpm. Renaming doesn't work in any LO-version, also tested with AOO - the same. Has been working at the beginning of XML Form Documents with OOo. There are descriptions available for OOo 2.0 which will show forms with many different named root-elements.
Comment 1 Buovjaga 2018-03-17 16:28:48 UTC
Not yet in 3.3, but already in 3.5. Must be something we copied from AOO along the way. Thus suspicious commits might be discoverable by reading AOO history around the time. On the other hand, might be really easy to fix anyway.
Tested on Win & Linux.
Comment 2 QA Administrators 2019-03-18 03:45:51 UTC Comment hidden (obsolete)
Comment 3 Robert Großkopf 2019-03-18 15:53:06 UTC
Bug still exists with LO 6.1.5.2 on OpenSUSE 15, 64bit rpm Linux
Comment 4 QA Administrators 2021-03-18 04:16:59 UTC Comment hidden (obsolete)
Comment 5 Robert Großkopf 2021-03-18 15:26:26 UTC
Bug still exists with LO 7.1.1.2 on OpenSUSE 15.2, 64bit rpm Linux
Comment 6 QA Administrators 2023-03-19 03:25:32 UTC Comment hidden (obsolete)
Comment 7 Robert Großkopf 2023-03-19 06:41:06 UTC
Have retested with LO 7.4.6.2 and also 7.5.1.2. Seems bug has been gone. InstanceData could be renamed without any problems.

I set this one to WORKSFORME.