You can add scripts/script triggers to go to the web viewer object to somewhat alleviate the issue.
I would suspect that there are underlying reasons why the current behavior is what it is, so I wouldn't necessarily bank on a change coming very soon, no matter how unfortunate that is.
1 of 1 people found this helpful
Thank you for your post.
A Web Viewer sits on top of the layout and uses the WebKit to display browser information. The Web Viewer will only become active when you click on it, so the suggestion by "CamelCase_data" to add a script trigger to select the Web Viewer active is excellent (Thank you!), assuming you have only one Web Viewer on the layout.
I am unable to move your post to the Product Ideas board, so I recommend also posting this information to the Product Ideas board at: Product Ideas
The Product Ideas board is monitored by Product Management and Development. All entries are read, discussed and considered for possible implementation in a future release.