[Libreoffice-ux-advise] [Bug 157482] Turn Security Warnings popup windows into infobars
https://bugs.documentfoundation.org/show_bug.cgi?id=157482 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Status|RESOLVED|VERIFIED --- Comment #12 from BogdanB --- Thanks, Balazs Varga, it works for all 4 cases. Verified with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0875594b381e2765f2b6413074c470f9eec33201 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 157301] Writer: repeat first column of a table on subsequent pages
https://bugs.documentfoundation.org/show_bug.cgi?id=157301 --- Comment #3 from Eyal Rozenberg --- (In reply to Stéphane Guillou (stragu) from comment #1) > I understand such a feature would depend on the ability of a table splitting > columns across pages as opposed to splitting rows Well, not necessarily. One could image a user doing the column-splitting themselves, apriori, but wanting the first column repeated. Example: A daily itinerary table, with different days on different pages. First column(s) should an hour range. Also, if this is implemented, remember the directions: * Of the table * Of the page * Of the paragraph and decide which of these should affect which column gets repeated. Probably the table direction. Also remember that, currently, the direction property of the table is labeled "Text direction" - even though it's not just the text direction (bug 157819). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 151928] Installation Wizard is not maximizable and requires UX improvement
https://bugs.documentfoundation.org/show_bug.cgi?id=151928 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #6 from V Stuart Foote --- See few benefits to attempting to provide CSD for the installation widget on Windows to support maximize or drag resize. As noted a default install has minimal user interaction, while a Custom installation on Windows already provides effective UI (for search & selection) with the MSI packaging defaults. Likewise, use of the MSI Installation Wizard defaults supports appwiz.cpl method to 'Modify' or 'Repair' an installation to adjust a custom installation. Our current implementation is suitable to task. IMHO => WF -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 157627] Paste number format only
https://bugs.documentfoundation.org/show_bug.cgi?id=157627 --- Comment #5 from Eike Rathke --- IMHO omitting the number format should not fiddle at all with the existing number formats of the target area, e.g. pasting a 10% (0.1) value would be displayed with whatever format was applied to the target cell, similar to pasting values only. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 157406] Writer allows to insert comments in footnotes in DOCX, but loses them
https://bugs.documentfoundation.org/show_bug.cgi?id=157406 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists | |.freedesktop.org| -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 157406] Writer allows to insert comments in footnotes in DOCX, but loses them
https://bugs.documentfoundation.org/show_bug.cgi?id=157406 --- Comment #6 from Mike Kaganski --- So is this a move towards limiting the UI for each external type, based on which file we open? So when we open a TXT, we should turn into a gedit clone? I do not see why should this be implemented. It would still be a problem, if one creates a new document, which then they would save as, say, DOCX. The important bit here is: (In reply to Nadie Nada Nunca from comment #0) > Writer ... doesn't give any warning about this. Well, technically speaking, it does: it warns by default, that saving to an external file format may loose data/formatting. If a user selects DOCX as their default file type, this warning would not show for DOCX; also, one may "do not show it again" in the warning - but in both cases, user tells that they know what they are doing. However: there is a longstanding issue of not having a *more detailed* warning about problems in export. We *may* provide details on export, if we postpone the warning until the export has collected the data for that; indeed, it would require some substantial work, and each such detailed warning needs to include some expansion notice like "Other incompatibilities may also happen", or the like... -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 157331] in automatic filter, add the number of the first row where the value appears
https://bugs.documentfoundation.org/show_bug.cgi?id=157331 --- Comment #5 from Heiko Tietze --- (In reply to hector from comment #3) > When any value in the list gives an error, that's what I mean. > > A user proposed the find/replace function from the drop-down menu. > > but it is not very comfortable. > > My proposal is for convenience, to identify the row where the first record > appears that has the value shown in the autofilter record list. > > > If you already have to put together the list that it shows you in memory, it > is also very complicated to show the row where that first value/error/not > available appears Can you share an example? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 151928] Installation Wizard is not maximizable and requires UX improvement
https://bugs.documentfoundation.org/show_bug.cgi?id=151928 --- Comment #5 from Heiko Tietze --- If you stick to the default it's just clicking trough four steps. The question was rather if we can make the installer resizable, not that I advocate for this. -- You are receiving this mail because: You are on the CC list for the bug.
