|
Okay, after some investigation, here is what I learned:
1. The bookbrowser uses the nav to generate mouseover strings that describe semantics and this model is auto regenerated like the toc window itself causing the nav to need to be parseable at almost any time.
2. After testing firefox, and safari browsers, and parsing errors in title or style tags in the head have to follow the rules for parsing html and gumbo does at well. The rules of parsing will cause the main body to hide inside head and result in an extra empty body being generated (gumbo does this too)
3. the NavProcessor will therefore take the gumbo/browser based code and fail to find any nav elements in the now empty body tag. This causes the NavProcessor to abandon the current nav as unvalid and start from scratch thereby doing the destroying.
So I will have to create valid nav detection code (probably using regular expressions) to be tried if gumbo/browser rule parsing ever fails before having it give up and throw in the towel.
I will try to rewrite the nav parser to be more robust and tolerant since it can be autoparsed at almost any time.
I will alert you when a fix is pushed to master. In the meanwhile, I do not recommend playing around inside the head tag of the nav, until this is fixed.
|