bits. Otherwise, display them as it is (e.g. utf8 byte strings) There shouldn't be the perfect way to let all strings display correctly in any cases, but this way all utf8 bytes and decoded strings should be shown fine if the HTML encoding is utf-8. (Thanks to tomyhero for reporting this)
This change is backward incompatible if you have your own panel subclasses. But I believe it's now much easier and more thread safe to write a panel. You can just implement one method (run) to preprocess and then return a callback to postprocess. Embedded panels are just Panel instances and your run method and a callback would just use its accessor to update title and content etc. Also removed a lot of docs from "your own panel HOWTO". I'm sorry for this but with the refactoring how to write your own panel is super obvious, and I don't think whoever has to write their own panel doesn't need this detailed guide.