I can confirm this using NVDA 2024.4.2 and Google Chrome Version 135.0.7049.96 (Official Build) (64-bit)
I also only started seeing this after the update to 6.8
Thank you for the workaround, but I hope this wasn’t a deliverate change and that it might get fixed sooner rather than later.