[Libreoffice-bugs] [Bug 96302] New: Wrong field variables and selections shown in Fields dialog.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

Bug ID: 96302
Summary: Wrong field variables and selections shown in Fields
dialog.
Product: LibreOffice
Version: 4.2.8.2 release
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
Severity: minor
Priority: medium
Component: Writer
Assignee: libreoffice-***@lists.freedesktop.org
Reporter: ***@nejko.net

Steps to reproduce:

1. Start LibreOffice Writer.
2. Select Insert>Fields>Other...
3. Enter a User Field, Text, Name v1, Value v1 and click Insert.
4. Note that v1 gets selected.
5. Select New>Text Document.
6. Note that v1 is still shown and is selected, even though there is no such
variable in the new document. This is definitely wrong. I now believe that the
expected behaviour would be that the Fields dialog should have been closed, as
I now understand that one may have one Fields dialog shown per open document.
7. Click on Insert.
8. Enter a User Field, Text, Name v2, Value v2 and click Insert.
9. Note that v1 is still selected even if Name/value shows v2. This seems wrong
to me.

I'm running this on Ubuntu 14.04 Desktop.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

Beluga <***@suomi24.fi> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |***@suomi24.fi
Summary|Wrong field variables and |Wrong field variables and
|selections shown in Fields |selections shown in Fields
|dialog. |dialog after creating a new
| |document with the dialog
| |still open
Ever confirmed|0 |1

--- Comment #1 from Beluga <***@suomi24.fi> ---
I see this on Ubuntu, but not on Win. On Windows the insert field dialog does
not have the user field v1. On Ubuntu v1 is carried over to the new document.

However, this is not true for me: "9. Note that v1 is still selected even if
Name/value shows v2."
After creating a v2 field with the Apply button, it inserts v2 to the new
document.

On Ubuntu there was some strange reaction when opening a new document with the
dialog open. It did some weird window focus switching ritual, perhaps 10 focus
switches, I thought it would crash.

Win 7 Pro 64-bit, Version: 5.0.3.2 (x64)
Build ID: e5f16313668ac592c1bfb310f4390624e3dbfb75
Locale: fi-FI (fi_FI)

Ubuntu 15.10 64-bit
Version: 5.0.3.2
Build ID: 1:5.0.3~rc2-0ubuntu1
Locale: en-US (en_US.UTF-8)

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #2 from Jan Skarvall <***@nejko.net> ---
Have a look again at step 9. v2 gets inserted, but in the selection view, v1 is
still selected. It bit misleading.

It may have been this "error" that made me think that the Fields dialog got
"out of sync", as I mention in
https://bugs.documentfoundation.org/show_bug.cgi?id=96301. That was before I
understood that a new Fields dialog pops up for ever open document.

Have you considered sharing a single Fields dialog?

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #3 from Beluga <***@suomi24.fi> ---
(In reply to Jan Skarvall from comment #2)

Post by b***@bugs.documentfoundation.org
Have a look again at step 9. v2 gets inserted, but in the selection view, v1
is still selected. It bit misleading.

Not for me.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #4 from Jan Skarvall <***@nejko.net> ---
So what is the semantic behind highlighting anything in the Select frame?

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #5 from Beluga <***@suomi24.fi> ---
(In reply to Jan Skarvall from comment #4)

Post by b***@bugs.documentfoundation.org
So what is the semantic behind highlighting anything in the Select frame?

What do you mean by this?

Again: v1 for me is not selected. Please upgrade to LibO version 5.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #6 from Jan Skarvall <***@nejko.net> ---
It seems that LibO 5 is not yet available on Ubuntu 14.04, at least if you
stick to packages that are supported. So, for now, I refrain from cluttering up
my installation, getting out of sync with the management of versions that the
Ubuntu Software thinks I have installed. Not (yet) willing to take the risk.

With the semantics I mean: How would you describe what the highlighting means
to a user? I think it will be tough to describe it if the highlighting does not
follow what is seen in the Name and Value boxes.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #7 from Beluga <***@suomi24.fi> ---
(In reply to Jan Skarvall from comment #6)

Post by b***@bugs.documentfoundation.org
With the semantics I mean: How would you describe what the highlighting
means to a user? I think it will be tough to describe it if the highlighting
does not follow what is seen in the Name and Value boxes.

But this is apparently the case only in versions prior to 5.

The remaining problem is that the variable from the older document is carried
over to the new, which is seen on Linux.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #8 from Jan Skarvall <***@nejko.net> ---
OK.Thanks for your time!

So, you agree that what I reported indeed are problems with the 4.2.8.2 version
and that the solution to the step 9 issue is to upgrade to Lib0 5, and that
there is not yet a solution on the step 6 issue for Ubuntu.

There is no option to indicate the particular Linux port as OS when classifying
the the bug report :-(. Should it be added as a keyword? Including Ubuntu
version? I don't know. Ubuntu versions changes content.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #9 from Beluga <***@suomi24.fi> ---
(In reply to Jan Skarvall from comment #8)

Post by b***@bugs.documentfoundation.org
There is no option to indicate the particular Linux port as OS when
classifying the the bug report :-(. Should it be added as a keyword?
Including Ubuntu version? I don't know. Ubuntu versions changes content.

It might be considered after we figure out how to display the Bugzilla lists as
treeviews: then "Linux" could be expanded and you would see some major distros.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #10 from Jan Skarvall <***@nejko.net> ---
Yes, but as I said, an Ubuntu release is not a static thing. A fault report may
be valid or not depending on upgrades that you made to the particular Ubuntu
version.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

Julien Nabet <***@yahoo.fr> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@yahoo.fr

--- Comment #11 from Julien Nabet <***@yahoo.fr> ---
You can find 5.0.3RC2 in LO ppa (see
https://launchpad.net/~libreoffice/+archive/ubuntu/ppa)

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #12 from QA Administrators <qa-***@libreoffice.org> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of
LibreOffice
(5.1.6 or 5.2.3 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of
LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat:
http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170103

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #13 from Timur <***@gmail.com> ---
I was willing to retest, but I didn't reproduce it at all in Ubuntu with LO
4.2.8.
Please add screencast and test in 6.0+.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #14 from Jan Skarvall <***@nejko.net> ---
I just tried to follow the steps to reproduce, and the problem is still there.

I am using LibreOffice Writer 5.1.6.2 on Ubuntu 16.04 LTS. LO 6.0+ is not
available on this Ubuntu version.

I do not know if there is something that I am not understanding.

It seems that my description of the behaviour in step 6 does not match the
behaviour I see now. It seems not to be possible to have one Fields dialog open
per document. If I try to open a new one having the second document, the dialog
is closed instead. If I then select the second document and open the Fields
dialog, there is no v1 variable, and if I then select the first document, v1 is
shown and selected, selecting the second document and v1 is missing as it
should.

But if I follow the procedure, i.e. not try to open a second Fields dialog, v1
is shown and selected irrespective of which document is selected. Going on with
step 7-9 also results in the behavior I reported.

I also noted that the creation of the second document sometimes is very slow.

Also, when I move the Fields dialog, and then change selection of the two
documents back and forth, the Fields dialog may change position, but not in a
logical way, which could be that the position is specific for each open
document.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #15 from Buovjaga <***@suomi24.fi> ---
(In reply to Jan Skarvall from comment #14)

Post by b***@bugs.documentfoundation.org
I am using LibreOffice Writer 5.1.6.2 on Ubuntu 16.04 LTS. LO 6.0+ is not
available on this Ubuntu version.

Thankfully you can free yourself from Ubuntu's version dictatorship by using
AppImages: http://libreoffice.soluzioniopen.com/

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #16 from Julien Nabet <***@yahoo.fr> ---
Also: https://launchpad.net/~libreoffice/+archive/ubuntu/ppa

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #17 from QA Administrators <qa-***@libreoffice.org> ---
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

--- Comment #18 from Jan Skarvall <***@nejko.net> ---
I tested using LibreOffice 6.1.3.2 on Ubuntu Desktop 18.04.1 LTS, and the
behaviour is now OK.

The current LibreOffice version on Ubuntu Desktop 18.04.1 LTS is 6.0.6.2 and it
has the erroneous behaviour.

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

Jan Skarvall <***@nejko.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |regression

[b***@bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96302

Buovjaga <***@suomi24.fi> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED

--- Comment #19 from Buovjaga <***@suomi24.fi> ---
Great news, let's close.