Bug 112875 - Hyperlink UI Window
Summary: Hyperlink UI Window
Status: RESOLVED DUPLICATE of bug 112117
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-04 12:16 UTC by JPSims
Modified: 2017-10-09 22:23 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description JPSims 2017-10-04 12:16:41 UTC 
Hyoerlink window in LO Calc (5.4.12). OS Windows 10. 
Hyoerlink Window frequently stretches across multiple screens. 
Hyoerlink Window does not allow itself to be resized manually.
Comment 1 Xisco Faulí 2017-10-05 08:16:36 UTC 
I can't reproduce it in

Version: 6.0.0.0.alpha0+
Build ID: 7901ede8a63f41aea707bd19c22f834253161378
CPU threads: 4; OS: Linux 4.10; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Comment 2 JPSims 2017-10-05 09:05:08 UTC 
Thank you for the quick response. I reset the user profile as instructed. That did not correct it.

Hyperlink Window still stretches across multiple screens. This has been an ongoing issue for me - off and on for 2-3 years and just been dealing with it. Now with current project I have many hyperlinks to input.

In the next LO update can we just give the user permission to resize the window manually or as needed?

Note Tried sending screenshot 4 times through the attachment page but keeps timing out after hitting submit button. Let me know how you would like the screenshot sent.
Comment 3 Adolfo Jayme Barrientos 2017-10-09 22:23:51 UTC 

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