Bug 141205 - FORM CONTROLS: Saving while a text box is focused will focus the next select input
Summary: FORM CONTROLS: Saving while a text box is focused will focus the next select ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.1.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Form-Controls
  Show dependency treegraph
 
Reported: 2021-03-23 16:44 UTC by Matheod
Modified: 2023-11-13 03:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Bug exemple (9.95 KB, application/vnd.oasis.opendocument.text)
2021-03-23 16:45 UTC, Matheod
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matheod 2021-03-23 16:44:31 UTC
Description:
Saving while a textarea is focused will focus the next select input

Steps to Reproduce:
1. Open the linked file (or create a text input and a select input)
2. Write some text in the text input and without leaving it, save the document

Actual Results:
The next select input will be focused

Expected Results:
The focus should have been kept in the text area


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.1.2 (x64) / LibreOffice Community
Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: default; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR
Calc: threaded
Comment 1 Matheod 2021-03-23 16:45:08 UTC
Created attachment 170666 [details]
Bug exemple
Comment 2 Dieter 2021-04-07 08:16:38 UTC
I can't confirm it with

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: f96004096268f5e71120678e32fc8c74055819aa
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test?
Comment 3 Matheod 2021-04-07 15:16:15 UTC
I confirm the issue is still here even in Safe Mode.

However I discovered there was additionnal step to make the bug trigger :

You need to scroll down to display the second page with the select input.

It's only after you do that that the bug will trigger.
Comment 4 Dieter 2021-04-07 15:33:32 UTC
Now I can confirm it it with

Steps to reproduce:
1. Open file from comment 2 (or create a text input and a select input)
2. Write some text in the text input
3. Scroll to second page (but cursor is still on page 1)
4. Save and reload
Comment 5 QA Administrators 2023-04-08 03:25:16 UTC Comment hidden (obsolete)
Comment 6 Dieter 2023-04-15 16:22:17 UTC
Same result in

Version: 7.5.2.2 (X86_64) / LibreOffice Community
Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL threaded

but I'm uncertain, if it is a bug or expected result. You have same result with every document: Take a document of at least two pages, add some text on page one and scroll to second page, save, close and reopen: Document always opens on second page.

Matheod, waht do you think? => NEEDINFO
Comment 7 QA Administrators 2023-10-13 03:16:31 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2023-11-13 03:12:31 UTC
Dear Matheod,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp