Helping the Apple Web Community w/o an Apple Computer?

ptaff asks: "Web developing can burn some braincells when trying to get a page to render fine in all browsers. Using XHTML/CSS on Win/Linux, thou can get a 'satisfying' result among PC browsers (MSIE, Mozilla-and-derivatives, Konqueror, Opera) - but when it comes to Apple browsers (Mac-MSIE, Safari, Omniweb, iCab, and others), and there's no Mac around to test, how can you tell if things will work out fine? I personally experienced a CSS border directive on an input tag that completely messed up a simple document. There are some CSS compatablity sheets (this comes to mind), but can you test further than that? is there any way a web developer can check for Apple-browser-compliance without a Mac?" If only HTML validation were as simple as submitting pages to the proper emulator, and viewing the results.

Comments

Re:[OT] Slash mucking

[forsetti]

Simple -- use:

&lt;rant&gt; == <rant>

Escape characters
Now this post was tricky to do !

Well, hey, not a new idea there

[devphil]

If only HTML validation were as simple as submitting pages to the proper emulator, and viewing the results.

Yeah, if only... oh, wait, it is.

Of course, testing for validation and compliance to standards is not quite the same thing as "does my web page look okay in Arbitrary Browser Foo," which is what the submitter was asking about. At some point you simply have to say, "any browser will work as long as it doesn't suck with regards to published open standards."

It's not the standards, people

[medeii]

This story's at three comments, and already I'm hearing that "if you just use standards, it'll be OK." That's a load of bull, actually. Standards make the cross-platform problem easier to solve, but there are always differences in interpretation of a spec. Safari has CSS bugs that Mozilla doesn't, and IE's Javascript parser does things differently than Opera's. Standards support helps this situation immensely, but by no means is it a panacea. I'm a big fan of designing sites that validate to XHTML 1.1 and CSS2 (and indeed, all of mine do), but it's still a lot of effort to come up with something that both looks good and works similarly and accessibly across five major browsers and three platforms.

My advice to the poster is to do one of three things:

1. Buy an iBook or Powerbook. They're pretty cheap, lovely to use, and you've got a good excuse for needing one. If your budget doesn't allow, check on eBay for a used G4 system (an eMac, for instance) and grab it instead.
2. Grab the only decent emulator I know of, Basilisk, and try to find someone with an Apple BIOS ROM and some System 7 CDs. That's as close as you'll get to emulating one, and no, it won't run OS X.
3. Use BrowserCam, a service that lets you (for a fee) see the results of your labor in a variety of browsers. It seems pretty cool, if you don't have any other option, but over time just buying a mac will pay for itself anyway.

Use Konqueror

[Anonymous Coward]

Safari uses the KHTML renderer from the KDE project. The same renderer is used by KDE for the Konqueror browser.

Apple's Safari team has already submitted patches to the KHTML code base. Over time Konqueror, and Safari will be the same. The one caveat is that Safari will have fixes, often before Konqueror due to a lag incorporating the Safari team's patches.

browser cam

[Galahad]

try the browser cam. CSS-D inhabitants swear by it.

check out zeldman et al

[4minus0]

I've been reading Zeldman's book Designing for Web Standards at safari.oreilly.com and it addresses this quite well. Safari and Mac IE 5.2 are very compliant to standards moreso than any version of IE on Windows, so it's not as big a deal now as it once was during the browser war era. Yeesh what a mess that was.

You can rest assured that as long as you don't code with a certain browser in mind your site(s) will look pretty close across platforms, IF you design with standards in mind. Losing table based layouts or at least minimizing their usage is one of the best things you can do to increase consistency across browser version/platform. Try not to use deprecated code either, like the venerable <br> or bgcolor = * and <P align="right"> etc. Always specify a DOCTYPE.

If you can move away from using old pre-war coding practices you'll be a step ahead in the fight. Check out these sites for more info on coding pages that look good in any browser on any platform:

• The Web Standards Project

• Zeldman's site of course.

• A List Apart

• Netscape's DevEdge is a great source of info.

• Validate your source.

• Validate your CSS.

• Another html validator.

• Accessibility is not only a good thing it's the right thing, especially if you ever make a government site.

• Bluerobot has some pre-cooked layouts to cut your teeth on.

Designing with XHTML and CSS means not leaving anybody out. From Web-enabled phones to IE 6 to text only browsers like lynx or links you'll only need to write your code once. I say do away with javascript browser detection scripts and write once, run (almost) anywhere!

There is a last resort you can go to if you must. Macromedia Flash looks the same in any browser provided you have the proper plugin. :) Although that is not my recommended solution.

Re:Should be simpler

[Khazunga]

Indeed, (X)HTML does not rigidly specifiy presentation. CSS, however, are a completely new business. They specify, down to the pixel, how layout and rendering should happen. That's their use.