If only we could see the second image.
It's really frustrating to know an image is there but not see it. There are other ways of sharing images with us. Instead of attaching them you are able to insert them inline so they appear right inside your post!
Just use the camera icon.
I can't help but to notice that the image with the missing scroll bar contains a scroll bar across the bottom. Does the popup appear with the vertical scroll bar if you scroll the page to the right?
Note that I'm not suggesting you should find this behavior to be acceptable and you should ignore it, but it may be a work around until we figure out a way to fix it (or until the developers issue a fix).
In the mean time, you should consider filiing a bug report on it.
When I click on the scroll bar at the bottom the pop up window disappears.
I just did some tests in RH8 and it all worked as it should.
Have you tried importing the two topics into a new project and testing the popup in that?
Not quite sure where that will get us in fixing things but let's worry about that when we get there.
See www.grainge.org for RoboHelp and Authoring tips
I upgraded another project and have the same problem with the auto-sizing box cutting off the scroll bar. In version 7 the user could click on an image and use the scroll bar to see more informaton (Frist image). In version 8 the scroll bar is cut off (Second image). When you try to scroll to the right on the bottom to see the scroll bar the pop up goes away. What is causing this?
Can you now try what I suggested? I am trying to identify if this is going wrong during the upgrade. Creating a new project is different to upgrading.
See www.grainge.org for RoboHelp and Authoring tips
In addition to my colleague Peter's excellent advice, you may also find you need to click Tools > Upgrade DHTML Effects in Topics... for the upgraded projects.
I sent in a bug report like you suggested and they responded that there is a bug. See their response.
Thanks for reporting this. It is a bug in RH8 and we are looking into fixing as soon as possible.
I am waiting for the fix. Due to work volume I had to go back to version 7. How long to fixes usually take?
Awwwww, man! Don't string me along like that! It's just twisted and gnarly and all knotted up!
We're seeing the same issue with multiple help projects that were upgraded to RoboHelp 8.
It seems to be an issue with eHlpDhtml.js. As a temporary workaround, we're replacing this file with an older version of eHlpDhtml.js (from RH7) after generating the help. Then popups display correctly. (If you use DHTML features other than popups, you might not want to do this. Popups might behave, but other features might break if they rely on the version 8 code.)
There's no way to replace the eHlpDhtml.js file in the source folder because RoboHelp 8 will just overwrite it with the newer version.
A minor issue, but it would be great to have it fixed. RoboHelp 8 is such a great product.
If you are really sure about using the version 7 ehlpdhtm.js, you can put the robo7 version in the directory's \Robohtml. Robohelp will use the script in that directory. Always make a backup of the original ehlpdhtm.js!
I personally use a php-script to copy some modified files from a network directory in my output folder. This way you don't have to overwrite any robohelp source files and still have the benefit of using your own files.
Great idea, Willam! Thanks for the tip.
I would just like to add that this issue also applies to popups that are sized to specific dimensions using the "Display in custom-sized popup" link option. In RH8, our fixed-size popups are not true to their RH7 counterparts. They are larger in both width and length, often (always?) placing the scrolling components out of view and inaccessible, as already described.
William's temporary 'fix' of copying over the RH7 version of ehlpdhtm.js does work, but, as already suggested, who knows what other issue this may cause.
So the question apparently remains, "how long is a piece of string?"
I have made some changes to ehlpdhtm.js file and now the clipping of popup isssue has been resolved.
I am attaching the ehlpdhtm.js file. you need to copy this file in your output folder and rename it to ehlpdhtm.js.
Note: This is still under development, and you should make backup of your project before going ahead with this change.
Please report back, whether this fix the clipping issue in popup or not, or if you find any other side effect of this change.
Adobe RoboHelp Team
ehlpdhtm.txt 128.8 K
I am attaching the updated file, again, please use it at your own risk, this is not a official patch, just wanted to help all out.
Please follow the steps given below
- Generate the webhelp output for your project.
- Open the webhelp output folder and rename ehlpdhtm.js file to any unique name like org_ehlpdhtm.js.
- Copy the attached ehlpdhtm.txt file in the webhelp output folder.
- Rename the ehlpdhtm.txt file to ehlpdhtm.js file.
Try running all your poup/related links/see also issues and let me know, whether this code change helps you guys or not.
Hope to see some positive news.
ehlpdhtm.txt 128.7 K
Thanks for going to the thread below and connecting it to this discussion.
It sounds like your changes to ehlpdtm.js may solve my problem with the related links (see also) menu. Before I start testing, I wanted to mention that I am using RH7. It appears, based on this thread, that the changes you made are for RH8. Do you think your file will work with RH7?
Please ignore my earlier question about RH7. I am using RH8. Guess it's too early in the day; I am not thinking clearly. I am on my way to testing your file.
You asked for feedback regarding the use of the modified ehlpdhtm.js file. I apologize if the post is thought to be lengthy, but the details may be important.
I tested your file in relation to the location of the see also/related topics links/menu position (issue in thread http://forums.adobe.com/message/2207682#2207682) and the scroll bar clipping issue.
I stored the file in the web help output folder as you suggested. Each time I generated the output, I had to replace the file in the output folder.
I stored the file in C:\Program Files\Adobe\Adobe RoboHelp 8\RoboHTML. This seems to have eliminated the need to replace the file in the output folder each time. It’s important to note that the location may be different for other people. I have not seen any other problems with this approach. If there are known problems with storing the modified file here, please let me know.
The location of the see also links menu is much improved. I did notice some (more) strange behavior. On some links, the popup menu appears just below the bottom edge of the button and almost out of sight below the edge of the browser window. You can see just enough of the top edge of the menu to know it’s there. It’s easy enough to scroll and see the complete menu and much better than the menu appearing at the top of the topic. In some instances, the menu is centered on the button, making it easier to see more items in the menu and know the menu is present. The number of items in the menu is the same in both instances. I have checked the placement and format of the button in both topics. Everything seems to be consistent.
As for the (web help) scroll bar displayed in auto-sizing popups, I noticed a couple of instances of the vertical scroll bar still being hidden. However, I could not recreate the behavior every time I opened the popup. I did find that the position of the popup was somewhat dependent on where you click the link, that is, the position of the pointer. If you click the first letter in the link, the popup is placed closer to the left side of the browser window. Clicking the last letter in the link displayed the popup closer to the right side of the window. In some cases, the vertical scroll bar was hidden.
I noticed also that the bottom of the popup extended below the bottom edge of the browser, which prevented me from scrolling to the bottom of the popup topic. Clicking the browser scroll bar to move the window to see the popup scroll bar closes the popup.
I could resolve the issues of not seeing the popup scroll bars using the mouse wheel to scroll vertically/horizontally. While this may not work for all, at least it may work for most people.
I noticed in HTML help, that the scroll bar in the popup could be hidden as well, even when using the modified file. I noticed that the position of the mouse, as explained earlier, is even more important in HTML help. It seems that every time you click near the end of the link, the vertical scroll bar is hidden. If you click near the beginning of the link, there is no problem. Again, using the mouse wheel, while a bother, you can bring the popup’s scroll bars into view. Another thought, is that the typical visitor may not know there is additional content and may not use the wheel.
Thanks for detailed information. This will surely help me in fine tuning the fix. I will get back with more refined solution.
Stay Tuned in
One more suggestion, Try changing the following option in RoboHTML 8. Go to Tools>Options and check the option Convert RoboHelp edited topics to HTML. Click OK and then generate the web help output and again replace the ehlpdhtm.js file. Now I hope you will see much better results.
Do let me know if this solves your popup issues or not. In the mean time I will try to find out why the solution does not work for XHTML files.
Thanks again for giving such a detailed analysis.
Thanks for your follow-up and continued efforts.
I selected the Convert RoboHelp edited topics to HTML option as you suggested. Good news! The see also/related topics links are working as I wanted and as they did in earlier versions. The popup menu is placed nicely next to the button. Also, another problem is resolved that I didn’t mention. I didn’t mention the problem because I thought it was just a behavior of web help. (I typically create HTML help.) The (words) links in the popup menu were underlined like a typical hyperlink. The color of the underline (words too I think) changed based on whether the link had been used. Now the line is gone. The appearance is much better. It seems that the see also/related topics links are working well in web help and HTML help.
I truly appreciate your help. My knowledge of RH is not deep enough to understand the workings of all the support files and changing those files. I am lucky there are people like you that are willing to help.
Good to hear that now the problem is solved. Hope this will help others as well.
Thanks for all the details analysis and giving feedback.
Hi Praful Jain,
I hope you are still monitoring this thread.
We, too, are having DHTML problems after upgrading from RH7 to RH8. The main one I've noticed is that popup links in topics that also include DHTML effects don't work, OR (more commonly) they don't pop up where they're supposed to but in some other position (often at the top left corner of the HTML Help window).
I copied the most recent version of ehlpdhtml.js from this thread and gave it a try, but it didn't solve the problem I'm describing.
I wonder if there is another version of that file that I can try -- or if Adobe has released a fix for this and related problems. It was reported months ago....
We'd appreciate an update on this matter. Thanks.
Can you let me know if the output is Webhelp or CHM? if CHM, can you share a sample project with few topics where this issue is happening.
The output is CHM. I only posted my question here because when I searched for popup problems, the hits led me to this thread. I will continue the discussion on the other thread.
Coming in late, here, so I'm looking to see if there are any updates, related to WebHelp usage.
We've updated to 8.0.1 and 8.0.2, but we've recently identified the same popup issues as others have (in this and other threads). The right margin of the popup has disappeared, and some portions on the right are off the screen if the popup link is in the right half of the screen.
- Is the ehlpdhtm.js file posted by praful_jain still applicable in our situation?
- Why should that replacement file only be used to overwrite the one in the WebHelp output (or was that an initial procedure recommended for testing only)?
- If the file needs to be replaced in the project source folder, shouldn't it also be replaced in the C:\Program Files\Adobe\Adobe RoboHelp 8\RoboHTML folder?
Note: My Program Files source is dated 9/8/2009, a project source file is dated 7/30/2009, and its related project output file is dated 12/1/2009 (the last date that output was generated). Shouldn't the project source file be dated the same as the Program Files source?
I added ehlpdhtm.js to C:\Program Files\Adobe\Adobe RoboHelp 8\RoboHTML, as you noted. I have not seen any adverse impact. By putting the file in the noted folder, I don't have to add it to the project source folder each time I generate the file. I recall (but you will need to confirm this) that if I placed the file in the project folder only it was overwritten each time I generated the project.
I found that the updated file did not resolve all problems related to the position of the popups. It seems the size of the IE window when you first open the popup might be an issue. However, most of my problems were resolved. For the few remaining issues, I found it easy enough to use the mouse wheel to see the edges of the popup. The problem related to the position of the related topics and see also popups seems to be solved completely.
I recently upgraded to 8.0.2. It appears that ehlpdhtm.js was not updated during the upgrade. The modified date of the file did not change during the upgrade, so I think the upgrade did not affect the file.
Thanks, Cal, I suspected as much about the update not changing the ehlpdhtm.js. I also seem to remember one of the Adobe peeps talking about a separate script they had created to handle this, or maybe it was something else (there's been so much activity concerning this file, different .dlls, special scripts, etc.). Sigh...
The issue is resolved in a script provided in a different thread.
Here is the related thread: http://forums.adobe.com/message/2446205#2446205
Here is another thread which, despite the title, also addresses auto-sizing popups and CHM output: http://forums.adobe.com/message/2368597#2368597
Here is the script: https://acrobat.com/#d=eJBek5hwjBpfC0gmP36n3w
(Read carefully, in case they do not address your specific issues.)
Hope this helps.
Auto-sizing popups in WebHelp (not custom popups, not .chm)
Popup Placement Fixer.jsx did not fix the issue of incorrect placement (right edge of popup hiding behind the topic scrollbar):
...nor did Custom Popup Size Fixer.jsx fix this issue (zero right margin):
God, I miss X502!
So, what now?
Good luck (and I really mean that!):
Is anyone continuing to monitor this issue, because it's still happening to me now (my pop-up windows appear at bottom right corner and they disappear when I scroll to them, the auto-sizing pop-ups have scroll controls that appear off the page). In addition, I have the added problems of my DHTML links for SOME links (I have an underline effect when users mouseover a link). The problem is evident even BEFORE I generate the WebHelp, when I use RH8's "View Selected Item" feature (Ctrl+W). An Internet Explorer Script Error window appears with the following message:
An error has occurred on this page
Error: 'style.pixelLeft' is null or not an object
Do you want to continue running scripts on this page? (Yes/No)
(Sorry, I could not attach the image to show you the window, so I just typed it out).
A similar message appears in my generated WebHelp (at the bottom of the IE window, it indicates that the file has some errors, when I click on it, it's the same ehlpdhtm.js error message).
I used Praful_Jain's latest ehlpdhtm.js file without any positive results. I just don't know what else to do. Are there any new developments/solutions/updates to fix this issue?
RH8.0.2, Windows XP, brand new project using the same stylesheet that worked fine with RH7. Generating WebHelp, not CHM, althogugh the problem appears before I even generate.
Thanks so much!!
I am still using version 7 and due to workload I have not had a chance to try version 8 again. Have you tried downloading the 8.0.1 and 8.0.2 updates from the Support Center? They were suppose to fix critical bugs.
I have RH8.0.2 now. Still having major problems. I miss RH7.