No full borders in complex tables around pictures




18 years ago
15 years ago


(Reporter: jhvr, Unassigned)



Windows NT

Firefox Tracking Flags

(Not tracked)




(2 attachments)



18 years ago
Build 2000120504 on WinnNT4 sp6b

I'm using a complex table. It has been working on Opera, Internet Explorer and
Netscape 4.76 pretty well. But one visitor claims that rendering the table is
wrong in Mozilla. I took the test. And yes, he's right.

Current result : not a full border around pictures.
Expected result: full border around pictures.
Reproducable   : always in Mozilla and Netscape 6/6.0.

Go to the URL:
Step 1: press home button in menu (wait for second window).
Step 2: choose 'aanmelden' (dutch for sign-in).
Step 3: use the link 'aangemeld' on the page (sign-in).

I made a small debug statement in the source: So you need to check in with a
sign-on name: MoZiLlA

Step 4: a new windows opens, here you type: MoZiLlA
(uppercase,lowercase,uppercase,lowercase,uppercase,lowercase, uppercase)

Step 5: press the button 'verzenden' (dutch for send).
Step 6: a new page will load with text: 'Gefeliciteerd MoZiLlA' (sign-on ok)
Step 7: press the button 'Venster sluiten' (dutch for close window).
(now you activated a small debug modus press Home in the menu, and you should
see the borders in the table!

You see, table rendering correct!

Now we go to the homepages by pressing 'Homepages' in the menu. And now we see
the problem. It might took you a while, but you are at the source of the problem!

If I take off the <a href=""></a> then the border is drawn 100% around the
picture! I know, it's cosmetic, but what the heck. Need to work well.

Friendly, HJ

Comment 1

18 years ago
CC,ing Jag, asked Jhim to verify this one, he's Dutch.
Keywords: helpwanted, verifyme

Comment 2

18 years ago
Ok, just send the request to Jag. Hope he will do it for us!

Comment 3

18 years ago
As soon as this stops crashing my browser :-)

Comment 4

18 years ago
Peter, what happening?
ALL the pages on this site are W3C validated HTML 4.01.
And ALL the stylesheet are W3C validated.
And ALL the XHMTL pages are W3C validated.
And ALL the javascript's are ECMA compliant!

What kind of build are you using? I'm using 2000120504 without any problems!
You are the first ro report this kind of problem!

Please let me know a.s.a.p.
Friendly, HJ.

Comment 5

18 years ago
Nope, nothing to do with your page, just a sucky browser ;-)

Could you perhaps reduce this to a simple testcase? That way we'll both know
more precisely what Mozilla is doing wrong. If you need help with that, find me
in #mozilla

Comment 6

18 years ago
I'm working on a single example file for that at this very moment, will let you
know as soon this is done. Thanks, HJ

Comment 7

18 years ago
Frist step done:
The function is extracted into tabel1.html on this URL:

This is an exact and 100% copy of the function used in a javascript called
jscript5.js on this site. And this works fine. But in this example, no framsets
are used, might that me the problem?

Take the test: Go to the site, sign-on with this name: MoZiLlA but do not use
the example, but the URL in URL on top of the page!
Now visit the homepage of one of the kids on this site. You now see a picture
with a full border on the picture! We are using the debug part now!

And after that, change your username into 'blabla' for example, does not matter,
this will only disable debug, and also <a href=""></a> is now used.

And by doing the same, visiting the homepage of one of the kids, you will
discover the problem. In the same function! In the same file!

I will take a look into that later!
Friendly, HJ.

Comment 8

18 years ago
over to HTML Tables.
Assignee: asa → karnaze
Component: Browser-General → HTMLTables
QA Contact: doronr → chrisd


18 years ago
Ever confirmed: true
Keywords: helpwanted, verifyme → testcase

Comment 9

18 years ago
Platform: PC
OS: Windows 98
Mozilla Build: 2001010204

Marking NEW.

Comment 10

18 years ago
Oh lord, my son did wipe out ALL the files in Mozilla directory, need to set up
a new one a.s.a.p.

Comment 11

18 years ago
the url works, the testcase not. 404

Comment 12

18 years ago
Created attachment 21934 [details]
Screenshot of the problem

Comment 13

18 years ago
Testcase is available starting from now, only is doesn't show the problem!?
It's the same code as on the site. Also loaded in a frame now. Blurk, what's
causing this then? Must be some sort of combination of different things. Brrr.
Must take a look into that, but you know, screenshot and testcase up and running!

Comment 14

18 years ago
The testcase/example triggers the bug starting from now!

Comment 15

18 years ago
Created attachment 22633 [details]
Reduced testcase

Comment 16

18 years ago
Now the testcase clearly shows you the bug. This bug is related to CSS. That
blue part with the red border is coming from the style a:link {}. 

1 - background should be blue, as in MSIE.
2 - border set for images should not mess with CSS a:link style and draw the
border around the picture of my son.

Now I know what seems to cause the bug, I guess this should go to Style System?

Comment 17

18 years ago
QA contact update
QA Contact: chrisd → amar

Comment 18

17 years ago
There is no border when the table is removed. Reassigning to attinasi.
Assignee: karnaze → attinasi


17 years ago
Target Milestone: --- → mozilla1.2

Comment 19

16 years ago
HJ I dont see that this has something to do with tables. 

Comment 20

16 years ago
attinasi will probably not work on those bugs :-(
Assignee: attinasi → table
QA Contact: amar → madhur
Target Milestone: mozilla1.2alpha → ---


16 years ago
Target Milestone: --- → Future

Comment 21

15 years ago
I think this is the same bug:
<a style="border:2px solid blue"><img src="spacer.gif" height=60 width=40></a>
in a nice small example.
In mozilla, the border shape is quite different from the image size.  Works in 
IE though ;)

This bug is invalid -- <a> is an inline element and the border/background of the
<a> itself does not depend on whether there is an image inside.
Last Resolved: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.