Bug 73903 - Check grammar as you type does not work for text in frames
Summary: Check grammar as you type does not work for text in frames
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Spell-Checking Frame
  Show dependency treegraph
Reported: 2014-01-21 23:15 UTC by tmacalp
Modified: 2021-05-26 04:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description tmacalp 2014-01-21 23:15:42 UTC
Live grammar checking does not work for any text inside frames.

Steps to reproduce:
1. Start a new writer document
2. Insert -> Frame
3. In the frame, type "This sentence has an  extra space."

The grammar checker should underline the error(double space) with squiggly blue as it does when the same error exists in the document's main body.

There is no blue squiggly underline showing us the error.

More info:
This seems to apply to all types of grammar checks.  The live grammar checks simply aren't performed on text in frames.  But if you actually perform a real spelling/grammar check (F7), the grammar errors in the frame are found.

I tested this on the following versions/environments and found the same broken behavior:
LO under 32bit Fedora17
LO under 32bit Fedora17
LO under 32bit Fedora17
LO RC under 32bit Fedora17

I also tested LO, but that appears to be before the inline grammar check was implemented.

I can only test, but I assume this bug has been around since in-line grammar was implemented in, so I've used that for the version.

I'm also limiting this to writer, as I am not able to check grammar at all in draw, calc, or powerpoint.
Comment 1 Dominique Boutry 2014-01-28 16:35:10 UTC
Reproduced with Lib0 rc on Win7
Comment 2 Joel Madero 2015-05-02 15:41:06 UTC Comment hidden (obsolete)
Comment 3 Olivier R. 2015-05-16 18:12:13 UTC
Comment 4 GABORIT Jean-Luc 2015-05-17 06:58:27 UTC
Reproduced with Lib0 Version: on Win7
Comment 5 QA Administrators 2016-09-20 09:41:37 UTC Comment hidden (obsolete)
Comment 6 Olivier R. 2016-09-21 12:35:58 UTC
Confirmed on LO 5.2.
Comment 7 Xisco Faulí 2017-09-29 08:48:37 UTC Comment hidden (obsolete)
Comment 8 tmacalp 2017-11-03 13:29:52 UTC
Can still repro in
Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4
CPU threads: 4; OS: Linux 4.8; UI render: default; VCL: gtk2; 
Locale: en-US (en_US.UTF-8); Calc: group
Comment 9 QA Administrators 2018-11-04 03:58:39 UTC Comment hidden (obsolete)
Comment 10 Olivier R. 2019-05-26 05:25:57 UTC
Still true with LibreOffice (x64).
Comment 11 QA Administrators 2021-05-26 04:53:14 UTC
Dear tmacalp,

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 https://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