ICEfaces
  1. ICEfaces
  2. ICE-1605

<ice:inputFile/> does not render <link> attributes from <ice:outputStyle> elements on the containing page

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6DR#4
    • Fix Version/s: 1.6DR#6, 1.6
    • Component/s: None
    • Labels:
      None
    • Environment:
      Tomcat 5.5.17 / Liferay 4.3.0 (pre-release)

      Description

      ICEfaces 1.5.3 used to have a "cssFile" attribute on the <ice:inputFile/> component, but this appears to have been removed
      in ICEfaces 1.6-DR4. That's OK, because it was kind of a hack.

      However, the rendered HTML within <iframe> still doesn't take on the XP theme or anything like that.

      Fixes attached.

        Activity

        Hide
        Neil Griffin added a comment -

        Search for ICE-1605 in the attached file for the fixes (two spots in the code)

        Show
        Neil Griffin added a comment - Search for ICE-1605 in the attached file for the fixes (two spots in the code)
        Hide
        Neil Griffin added a comment -

        Now that I think about it, the "cssFile" attribute is still needed in order to support portlet themes. I opened another issue so that this might get fixed as well:
        http://jira.icefaces.org/browse/ICE-1608

        Show
        Neil Griffin added a comment - Now that I think about it, the "cssFile" attribute is still needed in order to support portlet themes. I opened another issue so that this might get fixed as well: http://jira.icefaces.org/browse/ICE-1608
        Hide
        Adnan Durrani added a comment -

        Neil's suggested fix added so the iframe of the inputFile component can render css file links defined in the parent document.

        Note: I am wondering why "host + port" is required for external css file in portlet environment? As all other components are working without it. However in non portlet environment application-context is always a blank string and due to the complete URI without root-context it causes 404 (page not found) error. So I did not added host + port in the Uri.

        We need to test it with portlet.

        Show
        Adnan Durrani added a comment - Neil's suggested fix added so the iframe of the inputFile component can render css file links defined in the parent document. Note: I am wondering why "host + port" is required for external css file in portlet environment? As all other components are working without it. However in non portlet environment application-context is always a blank string and due to the complete URI without root-context it causes 404 (page not found) error. So I did not added host + port in the Uri. We need to test it with portlet.
        Hide
        Neil Griffin added a comment -

        Verified as fixed in ICEfaces 1.6-DR#5. I think this one can be closed.

        Show
        Neil Griffin added a comment - Verified as fixed in ICEfaces 1.6-DR#5. I think this one can be closed.

          People

          • Assignee:
            Unassigned
            Reporter:
            Neil Griffin
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: