FOP
  1. FOP
  2. FOP-1363

id attribute on fo:wrapper ignored (if fo:wrapper is a direct descendant of the fo:flow)

    Details

    • External issue ID:
      42423

      Description

      See <http://issues.apache.org/bugzilla/show_bug.cgi?id=41426#c4>:

      "Please note that while Adrian's fix removes the ugly ClassCastException,
      fo:wrapper will still not fully work as expected. You can use it to set
      inheritable properties but setting an "id" attribute will not have the desired
      effect. It will simply be ignored. The test wrapper_block_id.xml shows this."
      (-- Jeremias Maerki)

        Issue Links

          Activity

          Hide
          Glenn Adams added a comment -

          batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed

          Show
          Glenn Adams added a comment - batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed
          Hide
          Andreas L. Delmelle added a comment -

          Fixed in FOP Trunk.

          See: http://svn.apache.org/viewvc?rev=654111&view=rev

          Thanks for reporting!

          Show
          Andreas L. Delmelle added a comment - Fixed in FOP Trunk. See: http://svn.apache.org/viewvc?rev=654111&view=rev Thanks for reporting!
          Hide
          Andreas L. Delmelle added a comment -
              • FOP-1468 has been marked as a duplicate of this bug. ***
          Show
          Andreas L. Delmelle added a comment - FOP-1468 has been marked as a duplicate of this bug. ***
          Hide
          Andreas L. Delmelle added a comment -

          Status: Problem still exists in FOP trunk.

          The reason is that the fo:wrapper is a LeafNodeLayoutManager (and thus an InlineLevelLayoutManager),
          which works fine as long as the fo:wrapper does not appear directly under the fo:flow.
          For an fo:inline, this is prohibited by the Recommendation, so the issue does not apply there.

          Show
          Andreas L. Delmelle added a comment - Status: Problem still exists in FOP trunk. The reason is that the fo:wrapper is a LeafNodeLayoutManager (and thus an InlineLevelLayoutManager), which works fine as long as the fo:wrapper does not appear directly under the fo:flow. For an fo:inline, this is prohibited by the Recommendation, so the issue does not apply there.
          Hide
          Julian Reschke added a comment -

          ...the same problem may apply to fo:inline.

          Show
          Julian Reschke added a comment - ...the same problem may apply to fo:inline.

            People

            • Assignee:
              fop-dev
              Reporter:
              Julian Reschke
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development