Wednesday, November 03, 2004

My firefox is off.

With 11/1/2004 nightly build installed, my firefox got a very big space
under status bar.
Anyway, my firefox was very ill since I did an auto update and extension
auto update probably after 0.10.
Now, no response for any click.

Thursday, August 12, 2004

Use DIV instead of TABLE

After googling, I found a sample in
http://web.nwe.ufl.edu/writing/help/web/authoring/html/css/div.html

So, I came out a page like this :
.....
#menu {width:150px; float:left; display:block;}
#content {margin-left:25px;margin-right:25px;margin-top:5px;display:block; float:left;}
.....

<DIV ID="header" title="Header Area">
.........
</DIV>

<DIV ID="menu" title="Menu Area">
.........
</DIV>

<DIV id="content" summary="Page Content"></A>
............
</DIV>

Unfortunately, this layout was no good if I have a table inside content. The table got pushed down. Or, a style was with position:relative, then I got big space.
Therefore, I added style float:left to the content area. Now IE were good, but Mozilla. So, I added third line to dismiss content float to left.

#menu {width:150px; float:left; display:block;}
#content {margin-left:25px;margin-right:25px;margin-top:5px;display:block; float:left;}
#menu+#content{float:none;margin-left:175px;}

It's good at IE 5.5, 6, Mozilla, Opera, Safari IE 5.2, but IE 5.0.
At this point, I realized this kind of hacking was useless.

Then I looked at http://www.htmlite.com/SD008.php. Maybe, I should try position:absolute.
So, I had

#menu {position: absolute;left: 0px; width:150px;}
#content {position: absolute;left: 175px; margin-top:5px;}

.

In order to backward compatible, I added

TD#menu {position: relative;}
TD#content {position: relative; padding-left:25px; padding-right:25px; padding-top:5px;}

.

I were happy at this point. I could get IE 5, IE 5.2, IE 5.5, IE 6, Mozilla, Safari 1.0 and 1.2 looking right.
Only Opera wouldn't expand table inside content to 100% in a very special case.

Wednesday, July 28, 2004

The reality of Mozilla

Finally, Mozilla supports document.all. Script language supports to be
simple and easy to use. The document.getElementById is meaningful, but
academic. Mozilla should support document.all in the very beginning.
People treat W3C is standard, but W3C doesn't provide good solution in
some spec. I know IE lacks a lot of modern features and holding web
designer to do simple innovative design. And, I also can't understand
why some sites only code for IE, even government related sites.

I would be happy if Mozilla suite can read winmail.dat.

Anyway, I just try to be reality.

Wednesday, July 14, 2004

Surfin' Safari

I have HTML editor for both IE and Netscape and am waiting Safari to come to this game.
To make more compliated feature, like adding table, image, I relly DOM to construct the page. IE has a lot of proprietary method. It works, but I still prefer DOM standard.
The one big pain in IE is double line spaces for a enter key. This is very stupid thing - a P tag is inserted when enter key is hit whithout DIV tag nearby. I hop Safari not copying this behavior.

So far, I only use Safari 1.0 -- speedy, but bugs in JS and poor accessibility.
I don't have really chance to look at 1.2, but I really hope Apple can allow old OSX to upgrade to latest Safari.

Wednesday, April 21, 2004

I just get this account in blogger. Try to get thing start. The interface is easy in here, but I am confused by how to post. I thought the page I entered when I signed up was my first blog. Now, I am directed to create new post page. Anyway, it's my first blog ever.