Why everyone should use Safari for rich web development

Post by treyp » Fri, Jul 10, 2009, 3:30 AM UTC

arohner wrote: post #45

ruddzw wrote: post #6

"Basically, if some HTML/CSS works on Safari, the chances are very high it will work on Firefox 2 and higher, and on IE 6 and higher (with minor tweaks)." I don't get it. A lot of the hardship that comes with web development is that stuff that works great in modern standards-based browsers like Safari doesn't work when you try to view it in IE. I can't count the number of times I've taken a webpage that I developed t…

I'm new to web development, and I keep asking this question but I've never heard and answer to it: What's stopping us from making a tool that parses HTML/CSS and points out constructs that are known to be bad in certain browsers? Sort of like lint: "It looks like you're sending element foo inside element bar to IE6. This probably won't work right" I personally don't have a windows box to test IE, and I'm not looking…

Post by boucher » Fri, Jul 10, 2009, 6:26 AM UTC

olliej wrote: post #57

nuclear_eclipse wrote: post #50

Earlier quoted context omitted.

Because that's the way CSS/HTML works?

CSS and html both support rgb(), rgba(), hsl(), and hsla() colors in addition to hex...

Post by jpcx01 » Fri, Jul 10, 2009, 7:25 AM UTC

Maciek416 wrote: post #8

I really want to use Safari for debugging but every time I get down to trying to do so, I find some irritating hangup in terms of clunkiness and polish versus Firebug, and I end up heading right back to Firebug. Two things off the top of my head: 1) console output is just not as good as Firebug. Example: try going on jquery.com and doing console.log($("p")). Instead of a pretty printed array with styled items as in F…

Post by trezor » Fri, Jul 10, 2009, 8:23 AM UTC

rimantas wrote: post #40

trezor wrote: post #10

Earlier quoted context omitted.

Indeed. Sounds very much backwards to me. If anything, stuff developed to work with the restricted CSS-support in older MSIE versions (MSIE8 is actually not that bad) has a much higher chance of rendering correctly in Firefox, Opera and Safari than the other way around.

It may sound backwards but is it not. It is a broad topic and much can be said on this, but the short version is: it is always advisable to develop looking at more standards compliant browsers and then tweak it to work in IE. Usually it will take less effort. The reason for this is that IE let's you deviate more from standards, and then fixing it for other browsers will take more time. Also, other browsers albeit hav…