Closed Bug 240103 Opened 20 years ago Closed 20 years ago

Borders (set with external CSS) disappear on a few TD elements when a Javascript file is included in one.

Categories

(Core :: DOM: HTML Parser, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 240104

People

(Reporter: rjw, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7b) Gecko/20040408
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7b) Gecko/20040408

Borders (set with external CSS) disappear on a few TD elements when a Javascript
file is included in one.

Whilst build my site on my local network I had no problems with it at all, it
was only when I uploaded it to my web server did it start displaying the issue.
After some trouble shooting, it became apparent it was Javascript being included
that caused the problem.

Offending section:
<td colspan="2" id="date">
  <script src="script/dpdate.js" type="text/javascript"></script>
</td>
http://www.dynode.net/googleau.htm (might need to refresh this a couple of time
before the borders disappear)

Resolution:
<td colspan="2" id="date">&nbsp;
  <!-- <script src="script/dpdate.js" type="text/javascript"></script> -->
</td>
http://www.dynode.net/products.htm

While the script line is commented out (the non-breaking space is added for
expansion), my site renders as it should, but once the line is uncommented, it
breaks: the borders disappear and not just on the direct TD element, but also
the next TD element which is in a separate TR.

What's odd is the fact that this never happened while being developed on my home
network (gigabit), but only once uploaded to my web server where the download
speeds are slower: I could even reproduce the bug on my dads Windows XP machine,
running Mozilla 1.6 and connected to the Internet via dial-up--I believe it
might have something to do with rendering.

Reproducible: Always
Steps to Reproduce:
1.visit http://www.dynode.net/products.htm (Note the borders along the top and menu)
2.visit http://www.dynode.net/googleau.htm (If the borders are still there,
refresh a few times. If you're on very fast internet access, it may not work. I
use 512/128 ADSL and it does, Gigabit doesn't.)
Actual Results:  
Borders disappeared

Expected Results:  
Rendered the borders as it did whilst being produced on my home network.

Test cases:
Mozilla 1.6 on Windows XP
Mozilla 1.7b on FreeBSD 5.2.1-R
http://validator.w3.org/ validates, but I see errors in the source code:

http://www.dynode.net/googleau.htm

there is a closing </hr> tag, without a corresponding opening tag, suppose this
should be a tr, but then also the sequence /td /tr is broken.

<body>
    <table border="0" id="layout" width="100%">
      <tr>
        <td id="logo">dynode&nbsp;productions</td><td id="logo2"></td>

      </tr>
      <tr>
        <td colspan="2" id="date">&nbsp;
          <script src="script/dpdate.js" type="text/javascript"></script>
        </td>
      </tr>
      <tr>
        <td rowspan="3" id="mainmenu">

          <ul class="mMenuList">
            <li class="mMenuItem"><a href="index.htm">Home</a></li>
            <li class="mMenuItem"><a href="products.htm">Products</a>
              <ul class="sMenuList">
                <li class="sMenuItem">Google AU</li>
              </ul>
            </li>

            <li class="mMenuItem"><a href="">Services</a>
              <ul class="sMenuList">
                <li class="sMenuItem"><a href="">Design</a></li>
                <li class="sMenuItem"><a href="">Hosting</a></li>
                <li class="sMenuItem"><a href="">Support</a></li>
              </ul>
            </li>

          </ul>
          <hr />     <!-- shouldn´t this be a </td>? -->
        </td>        <!-- shouldn´t this be a </tr>? -->
forget my invalid comment #1,  <hr/> is valid xml.

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.dynode.net%2Fgoogleau.htm;ss=1;verbose=1

I don´t see missing borders, on a slow connection (64 kbit ISDN).

I´m duping this bug to the next one, to get rid of the invalid comment.


*** This bug has been marked as a duplicate of 240104 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.