WebView text, as opposed to url, input fails, important limitation maybe easy to fix??

[Psercom]

It was hard to find the message pump bug but at all the logical junctures where we might have given up, we were enjoying learning the code and really liking the whole endeavor so that inspired us to keep on.

Now, however, we did go back and flip on our test to see if WebView works from raw text as opposed to url input. Unfortunately, it doesn't even when we verify the other tag closure fix is active (buttons etc. are active).

So these are separate bugs.

We are hoping this second one might be easy for you to see and fix, knowing the code thoroughly.

Thanks for everything you've created here. It's magnificent.

[Psercom]

Text input to WebView becomes browser dependent since it's implemented through iframe so src/srcdoc come into play as well as e.g. audio tag vs audio in a further embedded iframe. It is inefficient but the issue workaround is to modify the desired text then write it to disk where WebView can handle it. The inefficiency is tolerable given the complexities of dealing with different browsers.
Frank may wish to close this issue given the tradeoffs and complexity.