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
// When the era field appears, mark it valid if the year field is already valid.
@@ -452,9 +452,9 @@ function processSegments(dateValue, validSegments, dateFormatter, resolvedOption
452
452
453
453
// There is an issue in RTL languages where time fields render (minute:hour) instead of (hour:minute).
454
454
// 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.
455
-
// 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.
455
+
// 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.
456
456
if(type==='hour'){
457
-
// This marks the start of the embedded direction change.
457
+
// This marks the start of the embedded direction change.
458
458
processedSegments.push({
459
459
type: 'literal',
460
460
text: '\u2066',
@@ -487,7 +487,7 @@ function processSegments(dateValue, validSegments, dateFormatter, resolvedOption
487
487
isEditable: false
488
488
});
489
489
}else{
490
-
// We only want to "wrap" the unicode around segments that are hour, minute, or second. If they aren't, just process as normal.
490
+
// We only want to "wrap" the unicode around segments that are hour, minute, or second. If they aren't, just process as normal.
0 commit comments