Nonscrolling region woes part deux...

[sanjsrik]

Hi all,

I've followed the directions to create a non-scrolling region in the help to the letter (help > creating a nonscrolling region). I associated a master page layout with my webhelp target it only contains a breadcrumbs proxy, no space below and a body proxy. I have a Heading1 style that i have in the non-scrolling region below my breadcrumbs proxy. the problem is that the heading1 nonscrolling style is part of the "body" proxy, so if I follow the instructions at the end of the topic for adding a nonscrolling region (steps 11- 14) for moving the content down to the be below the non-scrolling region, it moves ALL of my (including my heading1 nonscrolling region) text down down as well as my content that I just want to appear below the non-scrolling breadcrumbs and my heading1.

in other words this is what my topic (when including the master page) looks like:

breadcrumbs proxy
body proxy
(body proxy contains heading1, which is part of my nonscrolling region), but so too is my content. How do I separate out my heading1 heading style to not scroll but move the body proxy down so that it doesn't contain the heading1 as well as the content???

I'm thoroughly lost I've played with the margin top, margin bottom for both my body and my my breadcrumbs proxy. i've got the nonscrolling region set, but I don't want to have to put two hard returns before every first paragraph in every topic just to make them appear below the non-scrolling region. The instructions (steps 11-14 are not helping me to put the actual content below the body proxy if the non-scrolling heading1 is also part of the body proxy) are not helping.

help.

[i-tietz]

??? Really?
I have one div in the masterpage and another div in my templates and topics that are set to "fixed" and both divs don't move at all ...

Masterpage:
- div containing the topic toolbar proxy
- topic body proxy

Templates/Topics:
- div containing the h1 and almost always a table, too
- content

As mentioned above the divs are the elements which are set to "fixed".

[NorthEast]

(body proxy contains heading1, which is part of my nonscrolling region), but so too is my content. How do I separate out my heading1 heading style to not scroll but move the body proxy down so that it doesn't contain the heading1 as well as the content???

I'm thoroughly lost I've played with the margin top, margin bottom for both my body and my my breadcrumbs proxy. i've got the nonscrolling region set, but I don't want to have to put two hard returns before every first paragraph in every topic just to make them appear below the non-scrolling region. The instructions (steps 11-14 are not helping me to put the actual content below the body proxy if the non-scrolling heading1 is also part of the body proxy) are not helping.

The help instructions seem to work for me.

You mentioned the body proxy, but that isn't actually referred to in the help steps; check that you're applying the margin-top to the body style, and not the MadCap|bodyProxy style.

[sanjsrik]

(body proxy contains heading1, which is part of my nonscrolling region), but so too is my content. How do I separate out my heading1 heading style to not scroll but move the body proxy down so that it doesn't contain the heading1 as well as the content???

I'm thoroughly lost I've played with the margin top, margin bottom for both my body and my my breadcrumbs proxy. i've got the nonscrolling region set, but I don't want to have to put two hard returns before every first paragraph in every topic just to make them appear below the non-scrolling region. The instructions (steps 11-14 are not helping me to put the actual content below the body proxy if the non-scrolling heading1 is also part of the body proxy) are not helping.

The help instructions seem to work for me.

You mentioned the body proxy, but that isn't actually referred to in the help steps; check that you're applying the margin-top to the body style, and not the MadCap|bodyProxy style.

Yes, body, not bodyproxy. A typo on my part.

[i-tietz]

What about the "medium" in the stylesheet?
Could it be that you inserted the fixed region in the print medium or another irrelevant medium for the online help?

[sanjsrik]

I re-created my entire project, recreated the non-scrolling region, and it worked this time. Now, if I can just figure out what the other error I'm getting and why the error message means, i guess i'd be good.

[Craig.Prichard]

As a slight fork on this subject, I am using the non-scrolling region solution of a modified body { margin-top:...} with a fixed-region div and no changes to my MasterPage. What has me baffled is the fixed-region div has a light gray background (i.e. solid, not transparent) which renders as such in IE8, Firefox, and SeaMonkey. But in IE7 the background is transparent. When you scroll down the content passing under the div is visible.

Does anyone know about IE7 idiosyncrasies like this which I obviously don't know about but certainly need to?

Thanks.

[i-tietz]

Have you set the background-color of that div?

[Craig.Prichard]

It seems to be that IE7 doesn't like the color lightgrey spelled lightgray. To be safe I'm using #d3d3d3 instead and it works fine.

[Craig.Prichard]

Here's a piece of gold I found at David Walsh's blog (http://davidwalsh.name/ie8-emulate-ie7) on how to force your web page to be IE7-compliant. I placed the following in the <head>...</head> of my MasterPage.flmsp:

Code: Select all

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

If I have a { color: lightgrey; } (or background-color, etc.) in my CSS the Messages window in Flare (v6.1) immediately displays:

Code: Select all

drive:\path\filename.htm: CSS: Invalid color: lightgrey

When I change the spelling to lightgray or use #d3d3d3, the Messages window won't necessarily clear out the message but Flare knows the spelling is acceptable. If I close the project and reopen it, the message will be gone.

The only way I have found to fire off the message is to modify the CSS file and save it, i.e. force Flare to reload the CSS file. This action raises an event in Flare which causes Flare to evaluate the CSS for IE7-compatibility.

I am developing WebHelp on a Windows 7 system with IE8 for deployment in an XP enterprise committed to IE7. Since I don't know all the ways my current project might break in IE7, this meta tag in my MasterPage will force Flare to generate Messages during content creation (when Flare is forced to reload the CSS file).

I hope this helps others as much as it is helping me.