ICEfaces
  1. ICEfaces
  2. ICE-9851

New mobi:fetchContact 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: MOBI-Components
    • Labels:
      None
    • Environment:
      ICEfaces 4, BridgeIt app.
    • Affects:
      Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial

      Description

      Renders a button that can access the device contact list and allow selection and retrieval of a contact.

      ** Only supported on mobile devices supported by the native BridgeIt app. **

        Activity

        Hide
        Carmen Cristurean added a comment - - edited

        ICEfaces4 trunk rev# 40089
        Server: Tomcat7
        Mobile device: iPhone 4S/ iOS7/ BridgeIt1.0.4

        Test app:
        http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/fetchContact

        1) A JS error occurs if loading the demo (dynamicAttribute, h:dataTable, and other pages) on a desktop computer (FF27, Chrome33, IE10):
        Error in FF27:
        TypeError: ice.ace is undefined
        http://localhost:8080/fetchContact/fetchContactDynAttribute.jsf
        Line 66

        2) The rendered attribute is missing from the tlddoc.

        3) disabled, style and styleClass attributes don't work.

        4) Changing 'fields' attribute to either 'name', 'email', or 'phone' still returns the same value as for the default fields value ('name,email, phone').

        Show
        Carmen Cristurean added a comment - - edited ICEfaces4 trunk rev# 40089 Server: Tomcat7 Mobile device: iPhone 4S/ iOS7/ BridgeIt1.0.4 Test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Manual/fetchContact 1) A JS error occurs if loading the demo (dynamicAttribute, h:dataTable, and other pages) on a desktop computer (FF27, Chrome33, IE10): Error in FF27: TypeError: ice.ace is undefined http://localhost:8080/fetchContact/fetchContactDynAttribute.jsf Line 66 2) The rendered attribute is missing from the tlddoc. 3) disabled, style and styleClass attributes don't work. 4) Changing 'fields' attribute to either 'name', 'email', or 'phone' still returns the same value as for the default fields value ('name,email, phone').
        Hide
        Arturo Zambrano added a comment -

        Committed fixes for issues 1, 2, and 3 at revision 40304. Ffixed JS error by adding resource dependency; made component extend UIComponentBaseMeta for documentation purposes; added support for disabled, style, and styleClass attributes.

        Note that changing styleClass dynamically might not have a visible effect, dependending on which CSS properties are used, since the the jQuery UI button widget dynamically adds various CSS classes to the button that may override custom style classes. This can be solved by using the !important keyword in CSS rules or by simply having style classes that modify other properties.

        Issue #4 is a bridgeit app issue, since the component is rendering the correct value in the Javascript.

        Show
        Arturo Zambrano added a comment - Committed fixes for issues 1, 2, and 3 at revision 40304. Ffixed JS error by adding resource dependency; made component extend UIComponentBaseMeta for documentation purposes; added support for disabled, style, and styleClass attributes. Note that changing styleClass dynamically might not have a visible effect, dependending on which CSS properties are used, since the the jQuery UI button widget dynamically adds various CSS classes to the button that may override custom style classes. This can be solved by using the !important keyword in CSS rules or by simply having style classes that modify other properties. Issue #4 is a bridgeit app issue, since the component is rendering the correct value in the Javascript.
        Hide
        Ken Fyten added a comment -

        Remaining issue #4 spun off into MOBI-1036.

        Marking this resolved.

        Show
        Ken Fyten added a comment - Remaining issue #4 spun off into MOBI-1036 . Marking this resolved.
        Hide
        Arturo Zambrano added a comment -

        r41567: added 'tabindex' attribute to mobi:fetchContact.

        Show
        Arturo Zambrano added a comment - r41567: added 'tabindex' attribute to mobi:fetchContact.
        Hide
        Ken Fyten added a comment -

        Re-opened to add support for an optional "fallback" facet that will be rendered by the component if the BridgeIt app. cannot be used, either due to running on an unsupported platform (such as desktop OS), or the BridgeIt app. not being installed on the device.

        Show
        Ken Fyten added a comment - Re-opened to add support for an optional "fallback" facet that will be rendered by the component if the BridgeIt app. cannot be used, either due to running on an unsupported platform (such as desktop OS), or the BridgeIt app. not being installed on the device.
        Hide
        Arturo Zambrano added a comment -

        Added fallback facet to component at revision 41596.

        Show
        Arturo Zambrano added a comment - Added fallback facet to component at revision 41596.
        Hide
        Liana Munroe added a comment -

        Verified for Issues 1, 2, and 3 from description, Tab Index attribute and fallback facet. Icefaces 4 trunk r41775. Tomcat 7, FF 30, Chrome 35, IE 11, ios 7 and android 4.1.1.
        Issue 4 has been moved to MOBI-1036.

        Show
        Liana Munroe added a comment - Verified for Issues 1, 2, and 3 from description, Tab Index attribute and fallback facet. Icefaces 4 trunk r41775. Tomcat 7, FF 30, Chrome 35, IE 11, ios 7 and android 4.1.1. Issue 4 has been moved to MOBI-1036 .
        Hide
        Arturo Zambrano added a comment -

        r41782: modified fallback approach to determine in the client whether to display fallback contents.

        Note: the HTML structure of the component changed, so it might be necessary to modify existing tests.

        Show
        Arturo Zambrano added a comment - r41782: modified fallback approach to determine in the client whether to display fallback contents. Note: the HTML structure of the component changed, so it might be necessary to modify existing tests.

          People

          • Assignee:
            Ted Goddard
            Reporter:
            Ken Fyten
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: