ICEmobile
  1. ICEmobile
  2. MOBI-624

DateSpinner and TimeSpinner timeZone attribute has no effect

          Details

          • Type: Bug Bug
          • Status: Open
          • Priority: Major Major
          • Resolution: Unresolved
          • Affects Version/s: 1.2 Final
          • Fix Version/s: 1.4 Beta
          • Component/s: Faces
          • Labels:
            None
          • Environment:
            n/a

            Description

            The timeZone attribute on the DateSpinner and TimeSpinner has no effect. The timeZone can be changed on the component with no change to the bound date object, which appears to always use the default server time zone.

            The use of this attribute is also confusing as the component is used with the <f:convertDateTime/> tag, which has its own timeZone attribute:

            <mobi:dateSpinner useNative="true" id="date"
                                        value="#{dateBean.dateInput}"
                                        timeZone="#{dateBean.timeZone}">
                <f:convertDateTime type="date" pattern="yyyy-MM-dd" timeZone="#{dateBean.timeZone}"/>
            </mobi:dateSpinner>

              Activity

              Ascending order - Click to sort in descending order
              Philip Breau created issue -
              Philip Breau made changes -
              Field Original Value New Value
              Fix Version/s 1.3 Beta [ 10373 ]
              Philip Breau made changes -
              Assignee Steve Maryka [ steve.maryka ] Judy Guglielmin [ judy.guglielmin ]
              Philip Breau made changes -
              Description The timeZone attribute on the DateSpinner and TimeSpinner has no effect. The timeZone can be changed on the component with no change to the bound date object, which appears to always use the default server time zone.

              The use of this attribute is also confusing as the component is used with the <f:convertDateTime/> tag, which has its own timeZone attribute:

              <mobi:dateSpinner useNative="true" id="date"
                                                       value="#{dateBean.dateInput}"
                                                       timeZone="#{dateBean.timeZone}">
                                          <f:convertDateTime type="date" pattern="yyyy-MM-dd" timeZone="#{dateBean.timeZone}"/>
                                      </mobi:dateSpinner>               		The timeZone attribute on the DateSpinner and TimeSpinner has no effect. The timeZone can be changed on the component with no change to the bound date object, which appears to always use the default server time zone.

              The use of this attribute is also confusing as the component is used with the <f:convertDateTime/> tag, which has its own timeZone attribute:

              <mobi:dateSpinner useNative="true" id="date"
                                          value="#{dateBean.dateInput}"
                                          timeZone="#{dateBean.timeZone}">
                  <f:convertDateTime type="date" pattern="yyyy-MM-dd" timeZone="#{dateBean.timeZone}"/>
              </mobi:dateSpinner>
              Judy Guglielmin made changes -
              Fix Version/s 1.4 Beta [ 10874 ]
              Fix Version/s 1.3 Beta [ 10373 ]
              Judy Guglielmin made changes -
              Assignee Judy Guglielmin [ judy.guglielmin ] Steve Maryka [ steve.maryka ]

                People

                • Assignee:
                  Steve Maryka
                  Reporter:
                  Philip Breau
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated: