NYCPHP Meetup

[Michele Waldman]

I do not write ie or ff specific css.  As a matter of fact all of my
css/html works on any browser once debugged.

If you are writing specific browser code then your code is wrong.  I could
write a doc on tips for cross-browser css/html compatibility.  Like using
top and left instead of padding or margin.

Javascript is an exception.  There is necessity for browser specific, but
that can be streamlined somewhat.

But, to find all of your css/html bugs you have to test in all the browers.
I've found Opera to be the best at finding bugs.  But, every now and then
something in my html/css crops up in IE6.

It took me 3 months to figure out the right ways to code css/html without
specifying browser and cut that slop out.

Some doctypes seem to restrict javascript.  I've found that to be a problem
when the javascript in necessary.

I need my javascript and html/css to all work.  I like my php to work too.
;)

Michele

> -----Original Message-----
> From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
> On Behalf Of Peter Sawczynec
> Sent: Wednesday, June 03, 2009 9:49 PM
> To: 'NYPHP Talk'
> Subject: Re: [nycphp-talk] Periodic Browsercam.com group availability
> 
> This is just my exceptionally small irreverent dos centavos on this
> topic.
> 
> For about two years now, it seems one has been pretty much able to
> develop almost anything desired using virtually any CSS and any
> JavaScript (and using big heavy image files to boot) in 1000+ pixel wide
> designs and its all good.
> 
> And at this time, if one were to find that one needs to spend too much
> hard time reviewing browser compatibility issues, then it is almost
> axiomatic that the code itself is not sufficiently or democratically
> "cross browser and platform independent" enough in the first place.
> Essentially: a) don't use any IE specific code; b) don't use any code
> that does not run in IE; and c) especially important, don't use any code
> that don’t run in IE Mac. Just not ever. Do something else. Use some
> Flash gadget. If you don’t do a, b or c; all the code vets itself and
> will be browser independent and automagically run on old browsers too
> boot going way back.
> 
> Lastly, try to use <doctype> XHTML "Transitional" to be easy on yourself
> and all your friends. You'd be surprised how many "browser"
> compatibility issues are actually and simply <doctype> issues. "Strict"
> breaks a lot of CSS and indirectly the JavaScript code.  And that
> heartache is simply not necessary.
> 
> Then browser compatibility issues seem to just vanish.
> 
> Warmest regards,
> 
> Peter Sawczynec
> Technology Dir.
> blūstudio
> 941.893.0396
> ps at blu-studio.com
> www.blu-studio.com
> 
> 
> -----Original Message-----
> From: talk-bounces at lists.nyphp.org [mailto:talk-bounces at lists.nyphp.org]
> On Behalf Of Michele Waldman
> Sent: Wednesday, June 03, 2009 8:25 PM
> To: 'NYPHP Talk'
> Subject: Re: [nycphp-talk] Periodic Browsercam.com group availability
> 
> Don't work you aren't raining on my parade.  It's more like a trail of
> tears
> for me.  (If you don't know what a trail of tears is then you can Yahoo!
> It.)
> 
> I've had problems with running virtual machines on my computer.  The
> last
> time I tried it failed on me and I didn't have more time to look into
> it.
> 
> Using this website saves me from having a ton of more software loaded on
> my
> one overloaded ancient pc.
> 
> I don't need it extensively so it's a good solution for me.  If I was
> doing
> more heavy css testing I might have to consider something else, but it
> fits
> my needs of periodic testing.  If you have a group subscription then the
> price is nominal.
> 
> Plus, I don't test one at a time.  I select many browsers at once and in
> renders them all about 15 minutes later, while I'm doing something else.
> 
> If there's a specific problem, then I can put my attention to it.
> 
> Michele
> > -----Original Message-----
> > From: talk-bounces at lists.nyphp.org
> [mailto:talk-bounces at lists.nyphp.org]
> > On Behalf Of David Krings
> > Sent: Wednesday, June 03, 2009 8:11 PM
> > To: NYPHP Talk
> > Subject: Re: [nycphp-talk] Periodic Browsercam.com group availability
> >
> > Michele Waldman wrote:
> > > on with the development.  How many times have you thought, "I wonder
> > > what it looks like in IE6?"  So, join a group now.
> >
> > I don't want to rain on your parade, but isn't that something a VM and
> the
> > IE
> > package from Tredosoft can do? Does browsercam do something that the
> > regular
> > IE instances can't do? When I test browser based apps at work I have
> one
> > Windows VM and a Linux VM with all the popular and not so popular
> browsers
> > including IE from version 3.0 up. That covers all rendering engines
> and
> > about
> > all OS (after all Mac OS X is just a window manager on top of BSD, but
> I
> > also
> > got a Mac for testing). I recently transferred those VMs from
> Workstation
> > to
> > Server 2.0 so that I can run it one a different box. And with the free
> > TechNet
> > accounts that Microsoft gives out I could even run the IEs natively on
> yet
> > another set of VMs.
> >
> > David
> > _______________________________________________
> > New York PHP User Group Community Talk Mailing List
> > http://lists.nyphp.org/mailman/listinfo/talk
> >
> > http://www.nyphp.org/show_participation.php
> 
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
> 
> http://www.nyphp.org/show_participation.php
> 
> 
> _______________________________________________
> New York PHP User Group Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
> 
> http://www.nyphp.org/show_participation.php