An accelerator was added to the 'More' button at the bottom of the toolbar table button drop down in master, but it doesnt work. This was reported by V Stuart Foote in bug 84551 comment 25 and this is a confirmation of it.
Build ID: ced24ffba2fa1754c466b7944b0ee06d21292706
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-10-04_21:36:54
1. The More Options button opens Insert Table dialogue.
2. Ctrl + F12 brings up the Insert Table dialogue.
3. Selecting text and pressing More Options automatically converts text to table with no Convert Text to Table dialogue.
4. Selecting a row of text in a table and pressing More Options opens the Insert Table dialogue, after which the text is lost.
5. Individually multi-selecting text in columns in a row and pressing More Options automatically inserts another table.
All of this happens in previous versions.
Build ID: c4c7d32d0d49397cad38d62472b0bc8acff48dd6
Change to RESOLVED WORKSFORME.
Unfortunately this hasnt been fixed.
1) Click the 'insert table' button in toolbar.
2) Notice the accelerator underline under the 'M' in 'More Options...' button.
3) Press the letter M
Result: Nothing happens.
*** Bug 86678 has been marked as a duplicate of this bug. ***
There is a general problem of keyboard handling in floating windows. See Bug 76002.
Believe this is more than a GTK2/GTK3 issue as Windows builds are also affected.
On Windows 10 Pro 64-bit en-US (10586) with
Build ID: 49b5eed56c470975927bb7b0328337ab8a76a910
CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL;
TinderBox: Win-x86@39, Branch:master, Time: 2016-01-24_06:50:26
Locale: en-US (en_US)
STR as in comment 2 continue to reproduce.
** 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.2.5 or 5.3.0 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)
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!
This seems to have been corrected. STR as in comment 2 no longer produce issue.