ICEfaces
  1. ICEfaces
  2. ICE-9304

New ace:growlMessages component

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.BETA, 4.0
    • Component/s: ACE-Components
    • Labels:
      None
    • Environment:
      ICEfaces 3, ACE components
    • Assignee Priority:
      P1
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

      Description

      Add a new ace:growlMessages component that can be used in place of the standard h:messages or ace:messages components.

      The Growl Messages component will provide the user with a popup notification panel, similar to the OS X Growl component.

      There are several jQuery Growl components that we could leverage for this functionality, including this one:
      http://plugins.jquery.com/jgrowl/

      1. screenshot-01.png
        267 kB
      2. screenshot-02.png
        279 kB
      3. screenshot-03.png
        348 kB
      4. screenshot-04.png
        322 kB

        Activity

        Hide
        Ken Fyten added a comment -

        On 2013-10-07, at 11:41 AM, Cruz Miraback wrote:

        If the validator/required message contains single quotation marks (' ') a JS error occurs and the component does not display. The default message for f:validateLength tag contains single quotation marks so if using the default message with this tag the component will not render.

        In IE:

        Message: Expected '}'
        Line: 1
        Char: 299
        Code: 0
        URI: http://localhost:8080/growlMessages/growlMessagesDynamic.jsf

        In Firefox:

        SyntaxError: missing } after property list
        http://localhost:8080/growlMessages/growlMessagesDynamic.jsf
        Line 0

        Show
        Ken Fyten added a comment - On 2013-10-07, at 11:41 AM, Cruz Miraback wrote: If the validator/required message contains single quotation marks (' ') a JS error occurs and the component does not display. The default message for f:validateLength tag contains single quotation marks so if using the default message with this tag the component will not render. In IE: Message: Expected '}' Line: 1 Char: 299 Code: 0 URI: http://localhost:8080/growlMessages/growlMessagesDynamic.jsf In Firefox: SyntaxError: missing } after property list http://localhost:8080/growlMessages/growlMessagesDynamic.jsf Line 0
        Hide
        Cruz Miraback added a comment -

        Creating a test that contains a custom FacesMessage and in the summary/detail of that message I have an img element that points to an image. If escape=true then we would expect to see the HTML markup and not the image, and if escape=false then we would expect to see the actual image. Currently it isn't working as expected, the image will display regardless of the escape attribute value, so I think this may be a bug.

        Show
        Cruz Miraback added a comment - Creating a test that contains a custom FacesMessage and in the summary/detail of that message I have an img element that points to an image. If escape=true then we would expect to see the HTML markup and not the image, and if escape=false then we would expect to see the actual image. Currently it isn't working as expected, the image will display regardless of the escape attribute value, so I think this may be a bug.
        Hide
        Arturo Zambrano added a comment -

        Committed fix for 'escape' attribute at revision 38555. Now, escape=true should show the markup in the test above, and escape=false should show the image.

        Show
        Arturo Zambrano added a comment - Committed fix for 'escape' attribute at revision 38555. Now, escape=true should show the markup in the test above, and escape=false should show the image.
        Hide
        Arturo Zambrano added a comment - - edited

        I think there's no harm in having redundant attribute values in general. App developers can use whatever makes the most sense in their minds, instead of having to learn that autoHide=fatal is the same as autoHide=true. We'll leave autoHide=fatal for the sake of completeness.

        Show
        Arturo Zambrano added a comment - - edited I think there's no harm in having redundant attribute values in general. App developers can use whatever makes the most sense in their minds, instead of having to learn that autoHide=fatal is the same as autoHide=true. We'll leave autoHide=fatal for the sake of completeness.
        Hide
        Cruz Miraback added a comment -

        Thanks, confirmed JS error and escape attribute are fixed at revision# 38556 in Firefox24, Chrome30, IE10.

        Show
        Cruz Miraback added a comment - Thanks, confirmed JS error and escape attribute are fixed at revision# 38556 in Firefox24, Chrome30, IE10.

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Ken Fyten
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: