Scrolling this forum is infinite the page repeat itself in itself. Like a video larsen (safar v73)
http://www.emotionent.com/perl/yabb/YaBB.cgi?board=studio;action=display;num=1048096307
I've noticed that Safari doesn't render content as it comes in (i.e. it doesn't render anything on the window until it's done collecting response). Is this intended behavior? This will basically spell "sorry" to chunked content coming in hoping that they're incrementally getting viewed on the client-side...
could you confirm? thanks
Posted by dJsLiM at May 9, 2003 6:05 PMI'm wondering if anyone here could help me figure out what's wrong with the rollover/mouseout images I have in my website? In almost all browsers (including Safari), it didn't play all image frames in mouseout properly. The website's http://www.thebettsbro.com
Just so you know, I'm not posting my website's link just to get some attention. I actually need some help.
Posted by Adam Betts at May 9, 2003 9:00 PMWasn't XBL designed to kill babies and fat german tourists (http://bugzilla.mozilla.org/show_bug.cgi?id=50349)? It must be a powerfull language, if you can even style strange content.
Posted by bernd at May 9, 2003 10:19 PMMock XBL at your peril, puny human.
Adam: Safari indeed seems to have problems with mouseouts. For example mouse-outs on DIVs will not work, causing the DIV to remain visible (when used in popup menus). This can cause a lot of trouble...
Or maybe it are just badly designed pages showing that behaviour? Just tried a couple and couldn't get the error :)
I saw it here, but that can be intended (in the episode menu)
http://www.nbc.com/ER/episode_guide/index.html
Instead of adopting XBL, wouldn't it be better to adopt XML and XSLT? It feels ... more standardized.
Posted by simon at May 9, 2003 11:59 PMSure, XSLT should be implemented too one day, but XSLT doesn't solve the particular problem raised by Eric Meyer.
XBL provides a dynamic constrained transformation that can be altered on the fly. XSLT is a "transform once and lose the source" technology. With XBL, you preserve the source document as it was meant to be and adorn it rather than transforming it. For this particular problem, it's far superior to XSLT.
I love XBL, XBL rules, it only kills evil babies as far as I know.
I think, in theory, it could be even better than htc behaviors.
The can pour XSLT down the drain as far as I'm concerned.
Reminds me of a thread on the W3.org lists... (XSLT vs. XBL) ;)
XBL is a very powerfull language and actually works better then .htc. It would be great if it gets implemented in Safari.
Posted by Kunta at May 11, 2003 1:01 AM