Since the merge of the editable input fields in 4.x times, empty input fields completely vanish in the editor. Enabling the "field names" doesn't work for them anymore, and if they are empty we even miss the little gray indicator box, even with "field shadings" enabled. Lucky you, if you're navigating into the input field via cursor movement, so you can expand it. Hint: the "secret" key combo "Ctrl+Shift+F9" for the input field edit dialog finds it, even if it always starts at the beginning of the document. Overall the fields part of Writer definitely needs some love.
Probably I'll create a meta bug for an overall review of field handling in Writer. bug 101625 and bug 73386 are also related.
Created attachment 127101 [details] New LO game: find the input field
Confirmed with document. Arch Linux 64-bit, KDE Plasma 5 Version: 5.3.0.0.alpha0+ Build ID: cd72269a6a2c85ae9dd4552aa4808ef4fd1f6c0e CPU Threads: 8; OS Version: Linux 4.7; UI Render: default; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on September 21st 2016
** 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.4.1 or 5.3.6 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-20170929
Still happens on master (6.0) build from today, commit a3c2cce616c3a072ed7f7f8133b88db165ccbc5c.
** 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
Bug still exists on current master (commit 896a1f8630cc4948e23fc8cce926e4d0910feb96). This has always been a regression of the new input field inline editing code.
Reproduced in Version: 5.2.0.0.alpha0+ Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 Threads 4; Ver: 4.10; Render: default; but not in Version: 5.0.0.0.alpha1+ Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 Locale: ca-ES (ca_ES.UTF-8)
(In reply to Xisco Faulí from comment #8) > Reproduced in > > Version: 5.2.0.0.alpha0+ > Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53 > Threads 4; Ver: 4.10; Render: default; > > but not in > > Version: 5.0.0.0.alpha1+ > Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 > Locale: ca-ES (ca_ES.UTF-8) Hmm - never realized it did work at some point :-) $ git bisect log # bad: [ea0f3871e9b080744fc700c21e876d0ba9c663d5] 2015-11-25: source-hash-7289a140fc68dc898ba2b2357cc960968195f236 # good: [2b392af9c8f54629e3a3a98a8c92fa5af1c6722f] 2015-05-20: source-hash-90e2dabb8d0bb5382234be776c2ad0e2d5d9e224 git bisect start 'master' 'oldest' # good: [a8d19eafb9e195a85359dd8cdc5c46c38295caa0] 2015-08-22: source-hash-79fb61efb847405fa47235002b52ee8efad5e339 git bisect good a8d19eafb9e195a85359dd8cdc5c46c38295caa0 # good: [2ad98b12d82c4ada5756881f0d6074154976e95c] 2015-10-08: source-hash-2e6feddc53830406fa04b4a0aea49bb8438dc702 git bisect good 2ad98b12d82c4ada5756881f0d6074154976e95c # bad: [e4287d7f4aebf2543103c3dde6e1463edb50b8c2] 2015-11-01: source-hash-bf4c2f74de6b82177b5f047a96b7f8e0d54a9459 git bisect bad e4287d7f4aebf2543103c3dde6e1463edb50b8c2 # bad: [ffd755beebb0f92f13acfaaa658062bccdd80217] 2015-10-20: source-hash-2ce151c7de49f05072185dba7cd3e1945763ae2d git bisect bad ffd755beebb0f92f13acfaaa658062bccdd80217 # bad: [de900293a82dd9219f04242e4b93b62b7ff37d30] 2015-10-14: source-hash-78cf4ca4405d33d3f658da0d7f209afc8e6ee4a7 git bisect bad de900293a82dd9219f04242e4b93b62b7ff37d30 # good: [e24664683c04cb96f1c23581ed3e5c7c76bf800c] 2015-10-11: source-hash-143fb0a4b5d4ab69d4928299d8112ab95d99870a git bisect good e24664683c04cb96f1c23581ed3e5c7c76bf800c # bad: [f7669386ecda560d5defd15334eca5d482c7925f] 2015-10-13: source-hash-7c3c3006deaaaf1bb3f2f4eeeaf11da3bcebe53c git bisect bad f7669386ecda560d5defd15334eca5d482c7925f # good: [86d182346f7e79a4ef3dc36b1184ec1c0ff4721f] 2015-10-12: source-hash-898aff0d190b09d16cce866909b64cf023cba43f git bisect good 86d182346f7e79a4ef3dc36b1184ec1c0ff4721f # first bad commit: [f7669386ecda560d5defd15334eca5d482c7925f] 2015-10-13: source-hash-7c3c3006deaaaf1bb3f2f4eeeaf11da3bcebe53c Which has commit 5e1714fd7fcb ("tdf#77014 fix input field breaking of words at new line"). Reverting that fixes this problem, but bug 77014 is more grave IMHO. So we need a better fix for that one.