Mais oui! But damn frustrating. It took me two hours to put together that simple table! And I still have a kink in the last column that I can't get rid of.
It's like learning to play an instrument -- you appreciate how much effort really proficient people have had to put into learning how to do it.
Actually your code was about the same as mine. But I tried all sorts of approaches and didn't clean up debris from each try. If I'd known someone would be checking my code, I would have made it all more aesthetic looking! But very cool that you threw it together and got a cleaner result so fast.
If you're so smart, why don't you go to college? Oh, wait, I forgot, you are!
Well, I did learn something from going over your own source code. I haven't been putting a closing "/tr" tag at the end of each row, because my manual didn't indicate that it was necessary. But adding the closing tag to the two rows that had a problem -- immediately after the last data entry in each row -- completely solved the problem.
Thanks for the website referral. It looks interesting, but may be a little more in-depth than I need right now. I was thinking of just dropping by Barnes & Noble and picking up some recent elementary handbook.
HTML is fun, non?
ReplyDeleteMais oui! But damn frustrating. It took me two hours to put together that simple table! And I still have a kink in the last column that I can't get rid of.
ReplyDeleteIt's like learning to play an instrument -- you appreciate how much effort really proficient people have had to put into learning how to do it.
Well, looking at the source code on your page, the HTML you're using is odd. :P I can't figure out how it even works at all.
ReplyDeleteI spent a couple weeks learning HTML a couple summers ago, by the way.
ReplyDeleteWell, to begin with -- how can you read the source code on my page? LOL. Let's start with basics.
ReplyDeleteHaha, right-click--->view source.
ReplyDeleteThen a simple "find: hic" and it zoomed right to the table code.
Check this out. :P
ReplyDeleteGoddam smartass!!! :P
ReplyDeleteActually your code was about the same as mine. But I tried all sorts of approaches and didn't clean up debris from each try. If I'd known someone would be checking my code, I would have made it all more aesthetic looking! But very cool that you threw it together and got a cleaner result so fast.
If you're so smart, why don't you go to college? Oh, wait, I forgot, you are!
Well, I did learn something from going over your own source code. I haven't been putting a closing "/tr" tag at the end of each row, because my manual didn't indicate that it was necessary. But adding the closing tag to the two rows that had a problem -- immediately after the last data entry in each row -- completely solved the problem.
ReplyDeleteI don't understand why it works, but it does.
Most bad code can be interpreted by just about any browser, but it sometimes comes with issues. :P
ReplyDeleteOne issue being that large gap that's suddenly appeared above the caption!
ReplyDeleteI'm working out of a 1995 "how to" HTML book. There may have been improvements since then. :P
Oh, wow. That's several versions of HTML ago, and before CSS even showed up at all. :P
ReplyDeleteI would suggest this website.
HTML3, actually. :p
ReplyDeleteThanks for the website referral. It looks interesting, but may be a little more in-depth than I need right now. I was thinking of just dropping by Barnes & Noble and picking up some recent elementary handbook.