Not sure what you mean. Quick Sync is Intel marketing jargon for the HW/GPU H.264 encoder and decoder on board Sandy Bridge and later Intel chips.
VDA is an Apple Framework/API that supports decoding on external GPUs that include the Sandy Bridge or later HW decoders.
FFMPEG, VLC and Adobe Flash Player all support VDA.
Play a youtube video with Safari and check "stats for nerds" on Flash. It says: "accelerated video decoding". And it is a third party Adobe plugin.
Play the same video with Chrome: you will see video decoding is *not* accelerated and the computer heats up like crazy.
Either for lack of resources or for some other purpose (maybe difficult to integrate in their integrated flash player) Chrome does not support HW decoding via VDA.
Maybe it is. I always thought it was a vary undocumented and incomplete branch of Apple's API, which needs more help from Intel for it be fully supported for third parties. Why does it seem so under utilized?
Edit: Bingo,
this is why and (what I was trying to talk about), hopefully we see more use of Quick Sync in the near future because of this.
Okay, I'm slightly allergic to using JS for layout. If possible, I would rather use the word table like this:
http://jsfiddle.net/jz7ZP/2/
Won't work in <IE7 though. So the JS route would be better if you need to support those.
Note: using table for display is not the same as using actual tables so search engines won't penalise you for this.
Does not matter what people think. I just don't like chrome. It's got a lot of issues and it's a memory hog on the Mac. If you're coming from Windows maybe it's the best browser there is, I don't know since I only use Windows for testing, but for the Mac it's utterly crap.
As for my problem, I fixed it by setting min-width on the block, but I don't understand why chrome requires it when no other browser does.
I know that display: table isn't a real table, but I still don't like using it.
I'd still like to see a JSFiddle for your Chrome problem if you've got one.
Why would the best browser change depending on what OS your coming from? Just because
you are having a few problems with Chrome doesn't make it "utter crap"! It's not like Chrome's optimization is really awful, Safari's optimization is just really, really good.
I use Safari as my main browser, I love it, but I know how much good Chrome has done. Do you have any complaints about Chrome besides it not getting as much battery life as Safari, using a lot of RAM (see below) and having a few rendering inconsistencies (which don't happen that often to most people)? That sounds a billion times better then IE6!
As for the RAM usage, Safari has been known as a RAM hog too, I just did a test with 5 popular websites. Chrome was at 644.7MB and Safari was at 577.6MB, that's not that much of a difference.
Which doesn't really answer why Chrome is better than Safari, especially in since up until last year Chrome used Apple's code and the Safari engine.
I'm not trying to make people switch to Chrome from Safari, I'm saying that Chrome is a fantastic browser and it has pushed the web in new directions faster then ever. I use Safari myself and have since it came out. If Safari didn't exist I'd use Chrome.
Also both Apple and Google worked with
WebKit (which is Safari's engine and Chrome used it too). It is not "Apple's engine", WebKit is open source layout engine and used by many other browsers (mostly mobile). Apple and Google both contributed to WebKit and then Google forked it making Blink which they use now.
It's faster for me sometimes to use the keyboard shortcuts. Since I use Windows machines everyday for work, it's something I can't be without.
Regardless if prefixes are needed or not, the quick command does not exist in Safari as it does in Chrome, Firefox and IE.
Cmd + [ (for back) and cmd + ] (for forward). They've been there forever and remember you can always make your own keyboard shortcuts.
