ICEfaces
  1. ICEfaces
  2. ICE-3277

CSS attributes appear to get lost when navigating a portlet in IE.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: 1.7.1
          • Fix Version/s: 1.7.2
          • Component/s: Bridge, Framework, ICE-Components
          • Labels:
            None
          • Environment:
            portal portlet ie7 ie6
          • ICEsoft Forum Reference:
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            When ice:outputStyle is contained by elements other than HEAD, BODY, or FORM moving the declaration right before closing the tag the background image is rendered properly when navigating back to page1.
            Example:
            <ice:portlet>
            ......
            ......
            <ice:outputStyle href="..."/>
            <ice:portlet>

            Show
            When ice:outputStyle is contained by elements other than HEAD, BODY, or FORM moving the declaration right before closing the tag the background image is rendered properly when navigating back to page1. Example: <ice:portlet> ...... ...... <ice:outputStyle href="..."/> <ice:portlet>

            Description

            A forum poster submitted a test case that showed the calendar popup icon disappearing in IE when navigating between different views. I delved down a bit and it seems that it may be a more general problem with CSS getting "lost" as you navigate.
            1. ie7 calendar 1.png
              42 kB
            2. ie7 calendar 2.png
              41 kB
            3. ie7 calendar 3.png
              42 kB

              Activity

              Ascending order - Click to sort in descending order
              12 older comments
              Hide
              Permalink
              Mircea Toma added a comment -

              Links referencing CSS rules are supposed to be inserted into the HEAD element of the document. Although most of the browsers are forgiving where the links are inserted, I don't think we should rely on this kind of behavior.

              I believe a good way to fix the issue of CSS linking is to refactor ice:outputStyle component to use the ResourceRegistry API to insert the links directly into the HEAD.

              Show
              Mircea Toma added a comment - Links referencing CSS rules are supposed to be inserted into the HEAD element of the document. Although most of the browsers are forgiving where the links are inserted, I don't think we should rely on this kind of behavior. I believe a good way to fix the issue of CSS linking is to refactor ice:outputStyle component to use the ResourceRegistry API to insert the links directly into the HEAD.
              Hide
              Permalink
              Mircea Toma added a comment -

              I prototyped a version of ice:outputStyle component that uses the ResourceRegistry API but the results were not the greatest. The ResourceRegistry API is meant for serving up a resource while ice:outputStyle component just needs to reference one, regardless of how it will get materialized (sent over the wire). Also, as Deryk mentioned, we don't want to force a full page load on too often, especially in a portlet environment.

              Show
              Mircea Toma added a comment - I prototyped a version of ice:outputStyle component that uses the ResourceRegistry API but the results were not the greatest. The ResourceRegistry API is meant for serving up a resource while ice:outputStyle component just needs to reference one, regardless of how it will get materialized (sent over the wire). Also, as Deryk mentioned, we don't want to force a full page load on too often, especially in a portlet environment.
              Hide
              Permalink
              Mircea Toma added a comment -

              I attached a version of the plain HTML test case that mirrors better what the bridge does when an element is updated. The test case runs fine in IE, event with a CSS reference nested within the updated 'DIV'.

              Show
              Mircea Toma added a comment - I attached a version of the plain HTML test case that mirrors better what the bridge does when an element is updated. The test case runs fine in IE, event with a CSS reference nested within the updated 'DIV'.
              Hide
              Permalink
              Mircea Toma added a comment -

              I also deployed the war file to try reproducing the described issue but I could still see the background-image of the button after the redirect.

              Show
              Mircea Toma added a comment - I also deployed the war file to try reproducing the described issue but I could still see the background-image of the button after the redirect.
              Hide
              Permalink
              Mircea Toma added a comment -

              I'm marking this INVALID for now. I really need a well defined test case that can prove clearly that there really is an issue.

              Show
              Mircea Toma added a comment - I'm marking this INVALID for now. I really need a well defined test case that can prove clearly that there really is an issue.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Deryk Sinotte
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: