Page 1 of 1
HTML5 Index results weirdness
Posted: Mon Nov 03, 2014 12:26 pm
by Leon Descoteaux
Flare 10.2, HTML5
The subentries under the first result persist under the results for subsequent entries. For example, type "Agent" and get:
Agent
However, if you then type "Appliance" you first get those three "Agent" subentries, followed by the two "Appliance" subentries:
Appliance
- First
Second
Third
New one
New two
Before I email Support, I figured I'd see if anyone else had seen this and possibly had an explanation.
Re: HTML5 Index results weirdness
Posted: Tue Nov 04, 2014 5:31 am
by Leon Descoteaux
Disappointing result from MadCap support on this issue:
I was able to reproduce the behavior here. Please note that I have submitted a Bug Report on your behalf (#89818) with our development team and you will be notified via email if a fix for this is included in a future patch or release version.
And, of course, this potential future fix will (might?) come along well after we're supposed to ship this product with the current, ridiculous performance (see the screenshot; the green blocks are masking company name). Besides, my contract here will be up soon.
IndexPersistence.png
Say what you will about RH and its offshore support; an issue of this severity would have prompted a more immediate reaction and possible solution (adding files or replacing files instead of waiting for a nebulous "future patch or release version"). I think I'd rather provide no Index than one of this poor quality; how are we supposed to have users try clicking those links only to met with topics they've already seen in their previous search? And once they've figured out what I finally did (that those subentries are stale), their view of the integrity of our help will be greatly undermined.
Sigh...
Re: HTML5 Index results weirdness
Posted: Tue Nov 04, 2014 7:24 am
by Leon Descoteaux
As it turns out, the behavior only happens on local machines, but not the production version on our server. So, it looks like we're only affected in our own QA work, but the customer-facing output should be fine.