Thu, Jun 16
May 31 2022
May 25 2022
May 23 2022
May 19 2022
Thanks @Tsevener and @kostajh Becsause this effects the ability to click through on welcome messages and other key pages in any language with unicode characters and is in production, I'd say this is a pretty urgent issue for us. The scale maybe is medium/limited but the severity is bad (user experience is broken) and it seems like an equity issue that this works for latin characters but not other scripts. I don't think it is an unbreak now, but it is urgent for us.
May 12 2022
Thanks. Sent you the archive on Slack via the share sheet and it worked smothly on my end.
We do use language converter in a standard way across all languages with multiple character options. I'm not sure why Kazakh would have regressed specifically as no changes were made on our end. Will need to investigate if there is a config or upstream issue.
Likely a template or PCS issue as it is article specific. Dropping this to backlog.
I'm resolving this as other tasks have covered the individual strings.
Ok, yeah this seems to happen when the bar is not onscreen, so we need to make this accessible and in the right sequence, even when the view is not visible.
Ready for simple design on 6.9.2
Moving to 6.9.2 since 6.9.1 is basically ready to go with bug fixes.
May 10 2022
May 6 2022
Sigh... I hope people feel confident. I'm going to resolve this for now, and if feedback reveals continued issues we'll create new tasks for specific solutions we could consider.