Since new CSS Flexbox spec is Candidate Recommendation now and implemented in a few browsers (Chrome, IE10 and non-public Opera builds) it is time to add Flexbox support to Prince.
Haven't found it on roadmap and forum, so starting this feature request topic.
Yes, this would be helpful. Many modern grid frameworks utilize the flex-box model. This, along with lack of HTML5 support, are two major blockers for me.
Flexbox is now supported in all major browsers and the spec is in Last Call Working Draft state. We utilize flexbox pretty heavily in our site and would love it if we could use it in Prince as well. It doesn't just make vertical centering easier but obsoletes a lot of other layout techniques and hacks.
We are beginning our investigation of CSS flexbox layout and would welcome any relevant example documents you might have. In particular there are questions of how page-breaking will interact with flexbox.
as Flexbox support is a hot topic for us right now, please explain what example documents you need? Use cases, where Flexbox support would come in handy?
Yes, cases where you would benefit from it, and any examples we might like to test with as we develop flexbox support. In particular, any long content that may need to be split across multiple pages.
back again with three examples concerning equal height of containers, vertical alignment and ordering. But I believe the page linked to by hallvord covers these already.
(Now of course we need some longer texts using flexbox to make sure mikeday & co does the hard work thinking about how this should all work when paginated! )
I desperately need flex support, we automate adding 1-3 logos to certificates for hundreds of organisations, and those logos are all different shapes and sizes. With our digital certificates we just use flex to have them all aligned in a horizontal row but this is a nightmare with floats.
Progress! It is an active topic of development and we are passing some of the flexbox tests now. It's not in Prince 11, but we should have builds you can test early next year.
What about getting support up for non-reflowing pages? I am using prince to create one page marketing items and that text doesn't need to reflow—which I am sure is one of the bigger problems you are trying to figure out with supporting flex—and having flex support for that kind of layout would be very helpful.
We're nearing completion of our testing for the first release of flexbox. To give you an idea of progress, at the present time we pass most of the relevant tests from the W3C public test suite with the remaining test failures falling under the following categories:
paint ordering,
multicol flex items,
absolutely positioned elements in flex items,
poor performance for nested flex containers.
Please also note that we're not planning to support the following in conjunction with flexbox, at least in the initial release:
page breaking/fragmentation,
break-before/-after,
visibility:collapse,
vertical writing.
We ought to be able to release the first version by next month, assuming no major issues come to light. Please let us know if any of the features mentioned above are ones you might need, and thanks for your patience and support!
Flexbox is now available to try in the latest build.
We've now got multicol flex items and absolutely positioned elements in flex items working properly, and we've also improved the performance of nested flex containers. We're planning to work on fragmentation later this year.
Please give it a try, and let us know what you think.
I've discovered an issue with margin:auto. When I have a single line item using flex with a margin-bottom:auto, flex works well for both the browser and export. However, when I increase the font size so that the line wraps to two lines, the margin-bottom: auto doesn't work any more on export even though the browser preview looks good.
hi, just installed atest build for debian (prince-11.3-debian8.0-amd64.tar.gz)
...and flex seems not to be supported. had a div with display:flex and flex-direction:column but the elements in this div are positioned like display:block.
im also asking me why there is still the "prince-20160929-debian7.4-amd64.tar.gz"-build in download/latest while in packages is the above mentioned one?
sorry, me again but its not working. could instantiate prince but whe calling convert_file_to_file() it returns false. when i return to prince11.3 from the download pag (not latest) the pdf was generated. also log was not created, with the 11.3 it does log.
)