@kushari, Good news – looks like this was recently fixed. You should see the fix reflected in the next browser update to version 1.26x: