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
Or is this actually not a bug, since showing 12-hour time might be preferred to 24-hour timestamps? When I posted this in Slack, I said nightly vs. prod (in that order), but the screenshots shown were presented in reverse order, so could have been misleading.
If the idea is to use 24-hour clock, there shouldn't be AM and PM, so even if that is the intention, there is still room for improvement so your issue is still a valid one for me 👍
Ok, thanks for filing the issue. Having checked the code against the screenshots more carefully, I think this is not in fact a bug. brave/brave-core#10965 switched from a 24- to 12-hour clock representation, but if we're posting am/pm, that's more appropriate.
It is a bug that this format is hard-coded instead of using the current locale, but that's not a regression, so I don't consider it urgent. I filed #19452 to follow up.
Description
Article timestamp differs in nightly and release
Steps to Reproduce
https://www.indy100.com/news/subway-tuna-cattle-pork-chicken-b1956078
Actual result:
Expected result:
Perhaps the timestamp when viewed in
release
?Reproduces how often:
100% on this site
Brave version (brave://version info)
/cc @rillian
The text was updated successfully, but these errors were encountered: