search

Sonia1091 / dompdf

Automatically exported from code.google.com/p/dompdf
0 stars 0 forks source link

Support for position:absolute #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What would you like dompdf to do:

This position property is not currently supported.
Requested by Kjetil W. (shetil).

Original issue reported on code.google.com by ryan.mas...@gmail.com on 29 Apr 2009 at 6:08

GoogleCodeExporter commented 9 years ago 
The addition of this would be wonderfully helpful.

Thanks!

Original comment by rocknrol...@gmail.com on 2 Jun 2009 at 6:03

GoogleCodeExporter commented 9 years ago 
As well as position: fixed, to have the div on every page, as defined in the 
standard.

Sorry for flooding around this whole position support thing, but I also believe 
it'd
be incredibly helpful.

Original comment by tomd...@gmail.com on 4 Sep 2009 at 10:32

GoogleCodeExporter commented 9 years ago 
I think I've got the changes needed to support "position: absolute".  I added 
them a
while back for a project I was working on.  I'll talk to Benj and see if I can 
get a
patch to you guys.

Original comment by gregkiy...@gmail.com on 1 Dec 2009 at 4:43

GoogleCodeExporter commented 9 years ago 
Benj isn't actively working on the project at the moment. Can you get in touch 
with
Ryan Masten about the changes?

Original comment by eclecticgeek on 1 Dec 2009 at 5:45

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 27 Jun 2010 at 1:50

GoogleCodeExporter commented 9 years ago

Original comment by fabien.menager on 1 Feb 2011 at 8:53

GoogleCodeExporter commented 9 years ago 
It appears that in the latest beta absolutely positioned elements within a 
"position: relative" block do not render.  I had this working in the code that 
I contributed that is currently used for absolute positioning but in comparing 
the two I can't figure out what's changed.  Admittedly it has been a long time 
since I coded that stuff and I really have no idea what's changed elsewhere.  
Any chance someone has a simple fix?

Thanks guys!

Original comment by gregkiy...@gmail.com on 23 Aug 2011 at 11:11

GoogleCodeExporter commented 9 years ago 
I've started looking at this more carefully, and it appears that the issue has 
something to do with STYLE::$POSITIONNED_TYPES.  If I have a very simple html 
file with a single "position: absolute" div INSIDE a single "position:relative" 
div then the content of the absolute div is not shown.  If I then remove 
"relative" from the STYLE::$POSITIONNED_TYPES array then the absolute content 
is displayed, albeit overlapping the relative content.

I believe I've traced this behaviour to the renderer.cls.php(L190) file where 
it checks if the child_style->position is in the POSITIONNED_TYPES array, and 
if so, adds the frame to the stacking context instead of rendering it directly.

This is where I get stumped, as I'm not sure what to do to fix this issue.  If 
someone could let me know what the best way to debug the _stacking_context 
array in the page_frame_reflower.cls.php is, then I can try to proceed.

Original comment by gregkiy...@gmail.com on 30 Aug 2011 at 7:34

GoogleCodeExporter commented 9 years ago 
There have been a few changes related to absolute positionning in the SVN 
trunk, they may have solved this problem.

Original comment by fabien.menager on 31 Aug 2011 at 3:47

GoogleCodeExporter commented 9 years ago 
I am happy to report that the version in SVN fixes my issues.  Thanks for the 
great work picking up this project and continuing to take it forward.

Original comment by gregkiy...@gmail.com on 8 Sep 2011 at 8:39

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 24 May 2013 at 3:00