Created attachment 104541 [details] ZIP containing ODS and screenshot of behaviour under LOv4162, LOv4262, and LOv4304. Problem description: The text wrap option for a cell containing multi-line text with spelling errors appears to prevent access to the right-click spell-check context menu. The problem appears to be a regression since v4.1.6.2 and under v4.2.6.2 and v4.3.0.4 is influenced by whether the spelling error is on the first or last line in the cell. I have only tested with two lines per cell. A basic test example is attached. Cells B3:C4 (no wrap), B7:C8 (B6 wrap), and B11:C12 (B11 wrap) contain the test data. Each cell contains enough text to run over two lines when wrapping (Format > Cells... > Alignment tab > "Wrap text automatically" option checked - only B6 and B11 have this option set on). A spelling error ("spellig") is included to appear on either the first or second line in a cell. Right-click on a marked (and visible) miss-spelled word should offer access to the spell-check context menu (refer screenshot in attached ZIP). Steps to reproduce: 1. Ensure AutoSpellCheck is turned on (toolbar button "Abc" with red squiggly underline). 2. Open ODS in attached ZIP. 3. Follow the included instructions to try and right-click on a visible, miss-spelled (underlined) word in each cell containing test data. Current behavior: Spell-check context menu accessibility varies according to whether a cell in the same row has text wrap set on and whether the spelling error is in the first or last line of text in the cell. Expected behavior: Spell-check context menu is consistently accessible. I was not sure if this should be ACCESSIBILITY, UI, FORMATTING, etc. I would test this under a daily build but bug 82288 has undermined my trust (mildly) in these at present. If someone could test this on master I would be obliged. Thanks. Operating System: Debian Version: 4.2.6.2 release
Comment in this forum thread: http://en.libreofficeforum.org/node/8314#comment-34924 ... indicates I have duplicated a report. *** This bug has been marked as a duplicate of bug 81894 ***