Bookmarks are working in chm, but not in Webhelp output

[ktbFL]

I have one project that I have output both as a chm and as a webhelp project.  One one of the pages, I have some image maps linked to bookmarks on the same page.  These work fine in the CHM, but in the Webhelp, when I click on the image map area, nothing happens.  Am I missing a setting for Webhelp that makes these links work?

Thanks,

kb

(RH10)

[Captiv8r]

Hi there

Check the bookmark name. Is there a space in it? If so, eliminate the space and re-link it.

Cheers... Rick

[ktbFL]

oh, Rick... I was so sure this MUST be the answer... but alas... it is not... no spaces... at least i don't see one via Design or HTML views... see below:

All 4 of the bookmarks above are on the same page as the image that is mapped... See anything else I am missing?

Thanks!

[Captiv8r]

Hello again

Hmmmm, out of curiosity, is the page long enough that it is able to scroll to the bookmarked spot? Sometimes you have to position the insertion point at the end of the topic by pressing Ctrl+End, and press the Enter key 20 or 30 times so that you insert enough space for the page to scroll and position to the bookmark.

Cheers... Rick

[ktbFL]

It seems to be and they DO work in the CHM output which is puzzling to

me...

Ok... Here's one tidbit that might make a difference...

I have the book marks in drop down text... Now mind you, this works easily

in Flare... And when you click on the link, it not only takes you to the

drop down text, it OPENS the dd. However, with rh, the link takes you

only to the DD hotspot (heading) without expanding the DD (acceptable

because there's no other choice in RH). Again, this works fine in the CHM,

but not in the webhelp output.

[ktbFL]

OK... APPARENTLY... in Webhelp, bookmarks within drop down text won't

work...

After i sent the previous response i decided to try it out and see if that

might be the problem... and it so far seems to be.. need to publish the

files for our developers to try in the app... then I'll know for sure...

but for now, it's working in my Webhelp test output.

So sorry for the disturbance!