What is the best and cheapest iPage web hosting site for online stores?

Click Here To View All Answers...

Question I have... What is the best and cheapest iPage web hosting site for online stores? Hoping for any response. Another quick question... Since tables need to download before they can be displayed. I am wanting to break up a longer table into two shorter ones. Since I do not know html code, I basically need to stay with what I can do..

I want to remove the bottom border of the top table and the top boarder of the bottom table, so that you do not see the two middle boarders. Likely simple for those who know html..



<TABLE cellSpacing=0 cellPadding=0 width="100%" bgColor=#e1eef7 border=8>.







<TABLE cellSpacing=0 cellPadding=0 width="100%" bgColor=#e1eef7 border=8>.







How to remove the two boarders in the middle and still have 2 tables?.

Thanks in advance...

Comments (6)

Hmm... I need to find out myself. I don't know what is the right answer to your question. I'll do some research and get back to you if I got an anything. You should email the people at iPage as they probably can help you..

Comment #1


Make it a bit shorter though:.

Table.1 {border-style:solid;border-width:2 2 0 2px;border-color:#000000;}.

Border-width:2 2 2 0px; goes in a clock wise motion srating with top.

Dont use width & height like that (deprecated) add it into the css.

Table.1 {width:500px;height:200px;............}.

Always state units in css.


Bgcolor is also deprecated, put it into the css also background-color:#e1eef7;.

Also a good habit to quote everything, although not necessary, ie. border="8"..

Comment #2

Good posting, and nice answers..

I hadn't seen those CSS table attributes used like that before. Nice solution..

How many browsers support it?..

Comment #3

I agree, a good solution. But I have to agree with giz’s point about browser support. I can't help but think that way. Which is why I disagree with a lot of this talk of "deprecated" attributes being used, it’s safe and perfectly legal code where a Transitional doctype is used (loose.dtd)..

The whole purpose of Transitional code is to a certain extent backwards compatibility (poor browser support). Visual presentation as the w3c terms it. A lot of more up-to-date CSS falls over badly in older browsers. A lot of very experienced coders still use many deprecated attributes, purely and simply to gain better browser support. I am by no means a guru or the like but I’ve experienced it many times..

If browsers did offer better support (more importantly – perhaps the emphasis is on users to update them), then more strict code (strict.dtd) would render properly. On a similar note I’ve seen tons of strict code where many of the optional closing tags have been left in, again purely because some browsers make a complete hash of rendering what is 100% valid code..

I fail to see the relevance of pointing out deprecated attributes in Transitional code? Yeah, it conforms to the (strict) specs but millions of people simply don’t keep bang up to date with the latest browser releases, therefore I believe the author has got to code for the widest general support. Although I do agree about the use of "height", but in general, I disagree. Deprecated attributes are perfectly legal and valid code where a Transitional doctype is used, most importantly it allows better browser support...

Comment #4

I would use.

Border-right: #000000 2px solid.




Instead of just border: 2 2 0 2.

That way if fofr some reason you want a diff border style for weach side you can just change the solid to whatever..

Comment #5

Certain border attributes aren't supported by all browsers such as NN4, but border-style:solid and border-width are supported by all!!, yup even NN4.

A very nice 'table css' browser compatibility iPage site I came across (gone straight into my bookmarks).


Dork1337- yup, adapt it to how you need to use it,as someone said before 'there's many ways to skin a cat'.


I see your point of view, but as you can see i'm a 'fan' of keeping everything up to date..

From my logs 4% average use nn4, 3%misc, 93% ie5/nn6 and above. From my logs I could argue that people are getting up to date with their browsers...

Comment #6

I too am a big fan of valid code and always produce it, however I’m not with the school of thought of keeping everything bang up to date as it can make life very difficult indeed (poor browser support)..

Where the author has used a Transitional doctype, it may be mis-leading to quote deprecated attributes conforming to the strict.dtd. I just believe that consideration must be given to why they have coded to Transitional specs, nearly always backwards compatibility and flexibility..

However, I agree the most relevant point of all is as you say "many ways to skin a cat"...

Comment #7

This question was taken from a support group/message board and re-posted here so others can learn from it.