Yes, after Leopard is released. In description of Apple Cinema Displays you can find that Apple thinks they're using optimal resolution (for current pixel-sized OS). Leopard is expected to be resoultion-independent, so Apple may go for highest DPI then.
number of the things used in the acid2 test are to not likey to be high on their priorities and would be focusing on more widely used CSS
"Widely used CSS" is that tiny subset that works in IE6. Ofcourse nobody bothers using display:table-cell nor generated content when it fails in browser that 70%-90% visitors use, but these are very useful features.
No standarised/interoperable error handling is what haunts HTML. That's the real-world problem that Acid2 is trying to solve.
CSS2.1 is the "1.5" you're talking about. RTFA! It removes/changes all features of CSS2 that weren't interoperable in current browsers.
CSS is modular and can be implemented smaller chunks thanks to back- and forward-compatible error handling (it's not perfect though, but better error handling is considered doomed because of vendors dishonesty/sloppiness)
You mean chopping SVG like in SVG Tiny W3C Recommendation? Duh...
Click on a page (outside links and images), choose "block content..." and then click images. If this fails, click "Details..." on content blocker's toolbar and add rules manually.
Slashdot Mirror
Why does it take soooo many years to implement display:inline-block? (bug #9458 since 1999)
CD cover as JPEG. Inset as PDF.
Yes, after Leopard is released. In description of Apple Cinema Displays you can find that Apple thinks they're using optimal resolution (for current pixel-sized OS). Leopard is expected to be resoultion-independent, so Apple may go for highest DPI then.
It looks exactly like MS Office to someone who uses MS Word to write shopping list.
So connect three computers to the LCD and from the center you see Windows, Linux from the left and MacOS from the right.
Three computers? What a waste. We have virtualization these days.
Thanks. The aforementioned bug has been fixed.
Can someone point me to technical description of that Opera's brokenness? (I haven't found anything extraordinary on Slashcode's sf.net bug tracker)
I've got a gut feeling that's just yet another "It's not bug-compatible with $browser_i_love_so_much" kind of problem.
I can stream full HD content wirelessly - if it's compressed.
number of the things used in the acid2 test are to not likey to be high on their priorities and would be focusing on more widely used CSS
"Widely used CSS" is that tiny subset that works in IE6. Ofcourse nobody bothers using display:table-cell nor generated content when it fails in browser that 70%-90% visitors use, but these are very useful features.
System Preferences -> Keyboard & Mouse -> Modifier Keys... -> Caps Lock Key = Control (on Panther you'll need uControl tool instead)
RIAA and sensitivity? I'd rather believe that they've killed the guy themselves in a plot to get some good PR.
C'mon, this article has been called bullshit even on digg!
HD.264? High definition on 3-inch screen?
No standarised/interoperable error handling is what haunts HTML. That's the real-world problem that Acid2 is trying to solve.
CSS2.1 is the "1.5" you're talking about. RTFA! It removes/changes all features of CSS2 that weren't interoperable in current browsers.
CSS is modular and can be implemented smaller chunks thanks to back- and forward-compatible error handling (it's not perfect though, but better error handling is considered doomed because of vendors dishonesty/sloppiness)
You mean chopping SVG like in SVG Tiny W3C Recommendation? Duh...
Compare to myspace.
He's overapplied his own advice, to the point where his web site looks so generic that it has no unifying brand.
Really? I can recognize Nielsen everywhere - his website and books look all the same - ugly. That's his brand.
My statement is, if you have standards that NOBODY meets, then your standards are too high!
By this logic we shouldn't develop browsers beyond HTML/1.0. There always will be some browser with "too high" standards before others catch up.
You probably haven't been writing CSS much, if you think current browsers are good enough at it.
In what version of W3C's HTML have you found tabindex on <div> element?
There is no such difficulty in CSS2 (recommendation since 1998). That problem is unique to Internet Explorer, which doesn't implement CSS2 (yet!)
Click on a page (outside links and images), choose "block content..." and then click images. If this fails, click "Details..." on content blocker's toolbar and add rules manually.
You can add your own patterns to blocker, and they will work on iframes, too.
Seems pretty good. I've even found one example where Opera 9 beats FF.
Is NASA using cellphone cameras now?
2.5mb of MJPEG noise reencoded as GIF to show off 5x5 pixel spot?
Opera (which is Wii's wee browser) has support for 3d canvas in internal builds.
Latest build of Opera for S60 passes the Acid2 test and it does support AJAX, so Opera Software certainly won't let be beaten easily.