Quote:
Originally Posted by Peter Sorotokin
OK, I finally got some time to look at what actually happens in the code. The problem is caused by a long-standing bug in our code and a particular nesting of spans.
|
It's great to have some kind of official-ish answer, thank you very much. Your suggested workaround seems about the cleanest workaround possible (something cleaner would be a solution, not a workaround
).
A solution, of course, would be better, and while you're at it, you could fix the "display: oeb-page-header" thing
