Those bugs against Chromium have existed since 2008 and 2010 respectively, and have been closed by the Chromium team as either "fixed" or "wontfix". This behavior just started with NMSDK 5.6, is there a mitigation plan in place since Chrome is now the #1 browser by a rather substantial margin?
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
That's something we will be working with the development team on--they will need to do work to update their help calls from the existing online Help package to an alternative. Thanks for the feedback, Andrew!