Bug 143304 - Much Difficulty in Naming a file when saving
Summary: Much Difficulty in Naming a file when saving
Status: RESOLVED DUPLICATE of bug 126638
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.4.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-12 03:19 UTC by gentisle
Modified: 2021-07-12 11:10 UTC (History)
0 users

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 gentisle 2021-07-12 03:19:44 UTC
Description:
macOS Catalina 10.15.7, MacBook Pro 13, Intel, LibreOffice 7.1.4.2 a529a4fab45b75fefc5b6226684193eb000654f6.
When selecting File/Save or Save AS either from menu or icon on toolbar, several things different than the Windows edition. 1. the entire filename and extension are highlighted (selected), so that you cannot simply start typing the new file which of course, erases the "Untitled.odt (or .ods, etc). 2. Cannot paste over the "Untitled" with any file name. I end up saving the file as anything like, "H.odt", and then renaming. This method leaves the file out of the recent files list, since you have to rename it. Cannot paste into the saving filename dialog by keyboard or clicking the edit menu. Happens in ALL LibreOffice Components (Base, Calc, Draw, Impress Writer.

Steps to Reproduce:
1.File/Save (or Save AS)
2.Try to paste in the filename you wish
3.

Actual Results:
See above

Expected Results:
This field should be editable, and that includes being able to paste in a filename.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Mac OS X (All)
OS is 64bit: yes
Comment 1 steve 2021-07-12 11:10:56 UTC
Thanks for filing - sadly a known issue for a long time.

*** This bug has been marked as a duplicate of bug 126638 ***