oj-input-time component displays converted time

The behavior of the Oracle JET oj-input-time component has changed with the release of JET v12 to fix an issue where the component's default converter ignored the offset at the end of an ISO time string when the offset is provided. This means that the time now displayed by the component might be different from the time displayed in earlier JET versions.

For example, prior to v12, the component displayed the ISO time string T21:00:00+00:00 as 9:00 PM in the GMT timezone and 9:00 PM in the PST timezone, which ignores the offset (+00:00). The updated version of the component uses the offset to convert the displayed time based on the user's location, so T21:00:00+00:00 would be displayed as 9:00 PM in the GMT timezone and 1:00 PM in the PST timezone. If the ISO time string is provided without an offset (for example, T21:00:00 instead of T21:00:00+00:00), there is no conversion and the component will behave as it did in earlier versions, displaying the same time (9:00 PM) in all timezones.

If the updated component is not displaying the time that you expect, one workaround is to use the oj-bind-text component to display the time instead. Another workaround is to use the oj-input-time component and add your own converter:

<oj-input-time value='[[$current.data ]]' readonly="true"
 converter='{"type": "datetime", "options": "formatType":"time","timeFormat":"short","timeZone":"Etc/GMT-0"}}' >
 </oj-input-time>