Folks, Can you please review the attached patch and let me know what you think. If we decide to apply it to Trunk we are going to deliberately break the XSL-FO 1.1 Recommendation. I believe it’s something we want to do anyway, as I honestly think there’s a bug in the Recommendation on this regard; At least as far as basic-link is concerned.
I’ll launch a vote in a few days for the integration of this feature to Trunk. Thanks, Vincent On 11/02/11 15:57, bugzi...@apache.org wrote: > https://issues.apache.org/bugzilla/show_bug.cgi?id=50763 > > Summary: [PATCH] Size basic-link areas according to descendant > areas > Product: Fop > Version: all > Platform: All > OS/Version: All > Status: NEW > Severity: normal > Priority: P2 > Component: page-master/layout > AssignedTo: email@example.com > ReportedBy: vhenneb...@gmail.com > > > Created an attachment (id=26641) > --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26641) > Patch implementing the change > > The descendants of an inline-area are not taken into account when computing > the > height of the inline-area. > > The main real-life scenario is the following: when an image is surrounded by a > basic-link element, only a small part of it becomes active ("clickable"), not > the whole image. > > See full discussion there: > http://markmail.org/thread/d2a5p4dufipdgfp2 > > Bug report at W3C: http://www.w3.org/Bugs/Public/show_bug.cgi?id=11672 > > The attached patch breaks the XSL-FO 1.1 Recommendation and sizes basic-link > areas according to their descendant areas. More precisely, the > block-progression-dimension of the content-rectangles of basic-link areas is > computed so as to encompass all the allocation-rectangles of the descendant > areas. >