i turned off cookie and test as if ff is mobile browser.
and at the same mode, i develop some web page.

then jquery’s click event doesn’t work. i don’t know why it does..
so i turned on cookie and my js program works fine.
and that’s all.. there are too many mysteries in the browser.

i didn’t like ff2 because it freezed every two hour. it was very painful experience. so i use maxthon and safari (in mac) instead. now ff3 is released and my love is only for ff3. so many useful widget and cool themes. i’m totally satisfied!

but there’s one big problem in ff3. you can’t see youtube in ff3. i don’t know what mozilla think. isn’t it critical enough to fix right-now?

anyway, you can fix this problem by unstalling flash player 9 and installing flash player 10 beta.

http://labs.adobe.com/downloads/flashplayer10.html

now ff3 works like charm! ff3 provides 1st class web experiences. i have to uninstall other browsers

P.S. right encoding add-on is not updated for ff3 yet, that’ll probably make ff3 perfect.

because firefox is too slow and heavy, i decided to use safari yesterday. i changed my default browser in my iMac and set some bookmarks. it worked great and looked very clean and neat. i may miss some functionality of firefox, like foxytunes. but it’s ok by now. it’s fast and that’s just what i’ve wanted for so long time.

and also i installed safari 3 public beta in my vista. but it’s not so good as Mac version. i found some bugs in encoding and felt some awkwardness in look-and-feel. and though it’s very fast, not so much fast as i expect compared to IE(when opening just few tabs).

I may wait till beta is over. but i don’t likely to use safari in my vista machine.. (i love my maxthon so much!)

i noticed today that new flash player 9 for linux was launched one month ago.. (it’s because i’m a mac user now)

http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash

now we can use full-featured flash in most of computer  environment. that means you can get full secure flash-based ajax operation.

and i noticed also that there is a fantastic 3d desktop environment for linux.

http://beryl-project.org/

so cool, more than vista or osx..

now we don’t need to adhere to one monopole os or browser..
so many people tried and the world became more democratic and liberal.
it’s a trend, we can experience more pleasant and universal pc life, thanx for all developers!

whitehart is my favorite theme.. it looks so tidy. fits for me well.

https://addons.mozilla.org/firefox/364/

and also i use these add-ons

all-in-one gesture
cutemenus – crystal svg
del.icio.us 1.2
foxytunes
right encoding

i use only minimum set for avoiding crashes. (but it couldn’t prevent all freezes)
these are too enough for my daily web life.

actually, i’m not willing to recommend it, because it’s in beta state, somewhat unstable.. but i found it very useful or maybe i can say powerful than ever, so i post this article.

you can get it from http://www.getfirebug.com/

i could hardly image the web development without firebug, it’s only few weeks ago..

P.S. i got an lesson(you know my last post), even most great tools can’t make people smarter. if you’re fool, debugging time spent will be same whatever your tool is.. so in any case, don’t blame this splendid tool..

i searched ajax enabled browser info but there’s a few useful references in the google’s results. so i decide to make some..

from wikipedia
* Apple Safari 1.2 and above
* Konqueror
* Microsoft Internet Explorer (and derived browsers) 4.0 and above
* Mozilla/Mozilla Firefox (and derived browsers) 1.0 and above
* Netscape 7.1 and above
* Opera 7.6 and above

MSIE 4.0 is developed  in oct, 1997, packaged into Windows 98. in nov, 1997.
Safari 1.2 is packaged into OS X 10.3 in feb, 2004. hardwares installed OSX10.3 by default are iBookG4, PowerBookG4, PowerMacintoshG5, iMacG5. but in almost every OSX version ajax enabled safari can be installed.
there’s a few ajax enabled browser which supports apple’s os9. but who cares?
firefox supports ajax since nov, 2004, gecko engine 1.7 version is used.
any other browsers using gecko engine 1.7 started to support ajax since early 2005.
opera supports ajax since 7.6 beta but, that version was not released publicly. opera 8.0  released in apr, 2005 is the first public version.

i’ve seen many win98 machines working on my clients’ office. they don’t feel any impulsion about updating os. because office program and browsers work well in win98. so if you want to focus realstic browser support problem, only you have to concern is IE4. there’s one more issue on ajax, and this one is very critical. native XML DOM Parser is supported only by IE 5.5+& FF1.0+. i feel very uncomfortable about it.. we don’t have good native xml parser and json converter now. ( i plan to develop and add to my library someday)

IMHO, if the customers suffer from old-browser problem, you don’t need to change your script. just recommending installation of the newest firefox is enough in almost cases ^_^; it’s free and cool browser!

XMLHttpRequest was introduced in late 1997, but till early  2005, it wasn’t a main stream technology. or maybe i can say IE was prevailed so much at that time. 7 or 8 years there was only a few movement occured in web browser market. web programming was very quite and dull. but now it becomes very exciting.. i’m a very lucky guy living this ajax age

there was a big cross-browser problem when the  javascript’s history was started. you had to write quite different codes for IE and NN. at that time, i usually gave up the NN part, and i felt no guilty . for my excuse, it was all NN’s fault. but FF & Mozilla doing so well in these days, i always consider cross-browser issues when i make some web apps.

but there’s only a few site who treats only cross-browser problem. do you know about select tag bug in IE? select tag element’s z-index is  highest in IE, so you have to hide when you want to see some css animation in IE. there are so many problems like this. what i aim now is, not so perfectly cross-browser(mainly FF & IE) support javascript library targeted for japanese programmer. it may not so good.. but i need it madly for my project ^_^; there are so many javascript libraries in the world, only a few library is existed for japanese environment.

because this library supports major browsers only, the code is somewhat clean, and easy to implement. and though i give up the perfect cross-browser functionality, i always consider cross-browser issues. the main target i don’t want to support is a NN with document.layer. all other browsers will be supported as far as i can.

i wish the library will be finished someday not so far future from now. but i can’t assure anything.. anyway i started the project few days ago, and it works fine till now ^_^; wish my luck~

p.s. you may be surprised when you know there are so many people still using win98 & IE4. it’s because the hardwares aren’t worn out yet. still need 4-5years maximum. but probably they don’t need my web-apps, i sure. so i decide to ignore’em. and i feel no guilty at all

i upgraded FF yesterday. i hadn’t knew, because i was so busy to make something. there are many improvements and bug fixes, also some cool features added, but those may be useless for me.:-) most impressive thing occured in FF2.0 is improvement of tab browsing, now i can quit to use the buggy TabMixPlus. good. update process was smooth enough contrast to 1.0 to 1.5 upgrade case. overall i’m very satisfied.

new version of mplayer is available since 11, Jun, 2006.
it takes a year for new version, so a lot of parts are changed

http://mplayerhq.com/

it compiled so well in my openSuSE 10.1, unlike previous version ^_^;
just type like this

./configure
./make
./sudo make install

that’s all!

and in order to view MS media format, you have to download essential codecs package, it can be downloaded from same page. copy all codecs to /usr/local/lib/codecs

what i want is just playing wma to my firefox 1.5, so i installed mplayer-plugin too

http://mplayerplug-in.sourceforge.net/

it needs gecko sdk 1.8 when you compile, you can get  it from YaST or apt or ports or anything your modern os package manager.

./configure
./make

and

cp mplayerplug-in*.so /usr/lib/firefox/plugins
cp mplayerplug-in*.xpt /usr/lib/firefox/components

yeah! baby, yeah! you can see windows media format file is played in your linux firefox machine!

P.S. auto-play is not supported because of security problem. you have to right-click the mplayer module and select play.