From: Daniel Watkins <firstname.lastname@example.org>
To: Debian Bug Tracking System <email@example.com>
Subject: loadComponentFromUrl forces the window to full-screen
Date: Fri, 10 Oct 2008 12:30:43 +0100
When using com.sun.star.frame.XComponentLoader.loadComponentFromUrl to load a
file from URL into an XFrame, the window containing the frame is forced to
full-screen, and the desired geometry has to be reset. This shouldn't be
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it.
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
I can't provide an example for a report of 2008 and I never used the sdk so I can't write one myself.
Created attachment 148201 [details]
Opens new empty Writer doc from Launcher
This testcase does not imply the reported issue is valid, but may help figure out it is.
Python attached testcase file opens an empty page in fullscreen mode on Win7 platform.
Basic below testcase opens an empty page in fullscreen mode in Win7 platform.
Dim doc As Object, docProperties()
doc = StarDesktop.LoadComponentFromURL("private:factory/swriter", "_blank", 0, docProperties)
Dear Stéphane Aulery,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Problem persists with release 7.1 under Windows 10, using either Python or Basic.
(In reply to Alain Romedenne from comment #6)
> Problem persists with release 7.1 under Windows 10, using either Python or
Version: 220.127.116.11.beta1 (x64)
Build ID: 828a45a14a0b954e0e539f5a9a10ca31c81d8f53
CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win
Locale: fr-FR (fr_FR); UI: fr-FR