Bug 136713 - Standard toolbar 'Insert Table' splitbutton, with selection 'More Options' directly applies 'Convert -> Text to table' action, incorrect label?
Summary: Standard toolbar 'Insert Table' splitbutton, with selection 'More Options' di...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-13 10:13 UTC by Telesto
Modified: 2020-09-28 07:42 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-09-13 10:13:38 UTC
Description:
Select content gets a table click More Options

Steps to Reproduce:
1. open attachment 165449 [details]
2. Press CTRL+A
3. Table drop down -> Click more

Actual Results:
Content gets a table

Expected Results:
Table dialog


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
7.1

and in
LibreOffice 3.5.0rc3 
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Comment 1 Telesto 2020-09-13 10:14:36 UTC
Looks like a hidden feature something.. but not sure if this is actually used?
Comment 2 Heiko Tietze 2020-09-16 14:11:53 UTC
(In reply to Telesto from comment #0)
> 3. Table drop down -> Click more

What is the "table drop down"? If you talk about Table > Insert Table... applied to text, usually tab separated numbers, converting the text into a table, that's not a bug but a feature. It's the same as Table > Convert > Text to table (using Default table style).
Comment 3 Telesto 2020-09-27 10:00:14 UTC
(In reply to Heiko Tietze from comment #2)
> (In reply to Telesto from comment #0)
> > 3. Table drop down -> Click more
> 
> What is the "table drop down"? If you talk about Table > Insert Table...
> applied to text, usually tab separated numbers, converting the text into a
> table, that's not a bug but a feature. It's the same as Table > Convert >
> Text to table (using Default table style).

This about the 'table picker' in the toolbar; no clue how to call it.. and pressing 'more options'

Yes, this could be seen as 'feature' and as bug at the same time. Dislike putting thing where the don't belong. 
Table > Convert >> Text to table (using Default table style) is the 'clean' an proper way, IMHO.

However introducing such a feature isn't to hard. Getting it out will certainly trigger a "angry mob" somewhere (so suspect the answer to be 'leave it alone')

Other option would be to  to set it to low -> and introduce a new with a new category.. re-evaluate after 1 or 2 years :-). To be extended (maybe indefinitely). Or create a special meta-bug for open end design decisions. So there is 'temporal' solution; we set it to X or Y. And we might re-consider.

Instead of throwing into the not a bug or invalid area. Currently complains about UX being disappearing out of sight (by not a bug/or invalid). Which more or like burying it under the carpet. 

Prefer leave a single report about the topic open (in specialized meta bug). To keep tabs on the topic.. while holding on to they current approach.

So at least we know why we keep certain around and keep some track on complains (duplicates) and having a nice list of to be evaluated some day, some time. 
Yes, increasing the 'number of bugs' in the bug tracker; but I think the bug tracker will survive that :-)
Comment 4 V Stuart Foote 2020-09-27 14:21:58 UTC
Issue is labeling of options for the toolbar's plit button.

If the only action for the more options is to abble the text-to-table conversion, then just label it such?  Or do we keep the more options as that is consistent with other split-button handling?

IMHO => WF
Comment 5 Roman Kuznetsov 2020-09-27 17:21:20 UTC
That widget inserts a table and "More option" there inserts a table too anyway, just it makes it with more options and more input from user.
When you select a TEXT in the document and select "Insert table" then LO can do only one thing - transform that text to table.

I close this as NOTABUG
Comment 6 Telesto 2020-09-27 18:14:30 UTC
FWIW, is it allowed to create a meta-bug the keep track of the 'rejected' stuff; even as RESOLVED NOTABUG. Simply to keep track of the rejected?

To look up to check if it already discussed before etc (I certainly will forget it at some point); nor do I exactly now what others put forward in the past etc.
Comment 7 Heiko Tietze 2020-09-28 07:42:12 UTC
(In reply to Telesto from comment #6)
> FWIW, is it allowed to create a meta-bug the keep track of the 'rejected'
> stuff; even as RESOLVED NOTABUG. Simply to keep track of the rejected?

You better use the personal tag to keep track of your content. You can run a search for this tag and save the search so it's always close at hand.

A META tickets for your tickets makes not much sense for others and QA likely rejects this (happened to me too).