|
|
Posted by rfr on 08/18/06 20:44
What I sometimes do in situations like this is to employ a brute force
method.
I take the document apart and save each part, then put it back together
again, piece by piece until I find what it is that is triggering the
problem.
In your case, you might try taking pieces OUT, piece by piece.
I also should mention that you have a lot of code there that is
non-standard. Some coding is there BEFORE the <HTML> and some is there AFTER
the </HTML>. And you are trying to load an external CSS file within the BODY
section of your code. It is these features that led me to mention that you
validate your HTML. The problem triggering the malfuntion of the <HR> may
be caused by other malfuntioning HTML.
I sometimes find that a problem that is occuring in a specific area of a
document is being caused by some error "upstream", earlier in the document.
Look "upstream".
Your plea for help was felt here. I am not an HTML or CSS guru by any means.
I am as frustrated as you are over these quirks. I have a few of these going
on now too, mostly cross-browser issues. These tips on what I would do are
all I can do for you.
"Perth" <renaissance@australiamail.com> wrote in message
news:1155916722.694098.42160@m73g2000cwd.googlegroups.com...
>
> rfr wrote:
>> It would help you to validate your HTML code. Use GOOGLE to find the WC3
>> HTML vaslidator. The problem you are having may be with the none standard
>> code. For instance there is no </head> to end the <head>, and you are
>> loading external CSS stylesheets in the BODY of your document rather than
>> the header section. My best guess is that you have your <hr> rule WITHIN
>> a
>> div that is limiting its width . . .you can have the <hr> be 100% of the
>> div, but if the div isnt 100% of the document, then the <hr> wil be
>> constrained to whatever wiodth the <div> is.
>
>
> Thank you for your response. I added the omitted </head>, but I have
> looked at the </div> in all its instances, and it doesn't seem to be
> amiss. I really have looked at this. Still don't know what's wrong.
> I have not had this problem on the 300 or so other pages in which I
> have used this code in identical fashion.
>
Navigation:
[Reply to this message]
|