Summary: | Button OK isn't active when you try load content from external source | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Matthias Pförtner <matthias.pfoertner> |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | 79045_79045, danisproh |
Priority: | medium | ||
Version: | 7.0.4.2 release | ||
Hardware: | ARM | ||
OS: | macOS (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
Matthias Pförtner
2020-12-29 08:11:47 UTC
after inserting the link into the dialog you should press Enter key on your keyboard. Please try it This is working on LibreOffice for Windows only. I have created under Windows the Calc file with the access to the external data source on GDRIVE and it is working as explained. When I try to open this file on a shared drive under LO Vanilla on M1 MacOS, it is said the the "link couldn't be updated". I am using presently LO Vanilla 7.1.4.2 on MacOS and LO 7.1.4.2 Windows. no repro The OK button is really inactive. My steps: 1.Create a new LibreOffice Calc document. 2.Click on a cell in the table (A1 for example) 3.Go to Sheet ▸ Link to external data. 4.The External Data dialog opens. - In the field ▸ URL of external data source - inserted my URL Google Sheet. 5. Tap Enter (OK button is not active). - A dialog box will open (Select the Language to Use for Import). 6.Choose language. 7. Tap the button OK Additional Info: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 246f24ebc8227345f13784d9e2f055d813f3d24f CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: ru-RU (ru_UA.UTF-8); UI: en-US Calc: threaded Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: ru-RU (ru_UA.UTF-8); UI: en-US Calc: threaded Although the OK button is inactive, the import function works. I think it's a dupe of the bug 114994 *** This bug has been marked as a duplicate of bug 114994 *** |