You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -433,7 +438,7 @@ function processSegments(dateValue, validSegments, dateFormatter, resolvedOption
433
438
// There is an issue in RTL languages where time fields render (minute:hour) instead of (hour:minute).
434
439
// To force an LTR direction on the time field since, we wrap the time segments in LRI (left-to-right) isolate unicode. See https://www.w3.org/International/questions/qa-bidi-unicode-controls.
435
440
// These unicode characters will be added to the array of processed segments as literals and will mark the start and end of the embedded direction change.
436
-
if(segment.type==='hour'){
441
+
if(type==='hour'){
437
442
// This marks the start of the embedded direction change.
438
443
processedSegments.push({
439
444
type: 'literal',
@@ -445,7 +450,7 @@ function processSegments(dateValue, validSegments, dateFormatter, resolvedOption
445
450
});
446
451
processedSegments.push(dateSegment);
447
452
// This marks the end of the embedded direction change in the case that the granularity it set to "hour".
448
-
if(segment.type===granularity){
453
+
if(type===granularity){
449
454
processedSegments.push({
450
455
type: 'literal',
451
456
text: '\u2069',
@@ -455,7 +460,7 @@ function processSegments(dateValue, validSegments, dateFormatter, resolvedOption
0 commit comments