Summary: | Float tables/images/frames across page boundaries | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Daniel <daniel> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | enhancement | CC: | aron.budea, daniel, davost, heiko.tietze, jmadero.dev, moritz.ulmer, osmano807, robinson.libreoffice, zen |
Priority: | medium | Keywords: | needsDevEval |
Version: | Inherited From OOo | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=89082 https://bugs.documentfoundation.org/show_bug.cgi?id=112704 https://bugs.documentfoundation.org/show_bug.cgi?id=49258 |
||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 107656, 107707, 108437 |
Description
Daniel
2011-09-14 06:39:41 UTC
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian Moving to UNCONFIRMED as this hasn't been independently confirmed by QA team - thanks for your patience and understanding. (In reply to daniel from comment #0) > This is a very old feature request raised for OpenOffice in the year 2004 > (http://openoffice.org/bugzilla/show_bug.cgi?id=35545). Updated URL: https://issues.apache.org/ooo/show_bug.cgi?id=35545 "Float tables/graphics across page boundaries like LaTeX" > Expected result: > Often, people want to avoid large white spaces. The picture should have a > parameter allowing subsequent text to be pulled to the page before the > picture. This is known as floating objects in other environments such as > LaTeX and applies even to other objects such as tables. Plausible enhancement request. Handing to UX Team for further triage. Status -> NEW We're replacing our use of the 'ux-advise' component with a keyword: Component -> LibreOffice Add Keyword: needsUXEval [NinjaEdit] Bug #89082 is similar, naming the same type of problem for frames, and a workaround is provided specifically for images, but possibly will work for other types of object. Don't see how UX can contribute at this stage. Removing the keyword. |