Re: PHP Manual problems
| From: | Ashley Sheridan | Date: | Wed, 10 Feb 2010 18:24:34 +0000 |
| Subject: | Re: PHP Manual problems | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-301948@lists.php.net to get a copy of this message | ||
On Wed, 2010-02-10 at 13:25 -0500, Robert Cummings wrote:
>
> Michael A. Peters wrote:
> > Bob McConnell wrote:
> >
> >> Our SOP is to generate standards compliant pages, validate them with
> >> Firefox and the HTML Validator add-on, then deal with the deviant
> >> browsers. It's a lot less work than trying to do it the other way
> >> around. There are a few minor issues, such as W3C still refusing to
> >> allow the autocomplete attribute for forms, while PCI requires it. But
> >> those are few and far between.
> >
> > Go HTML 5.
> > It doesn't work with the validator plugin but it validates at W3C.
> >
> > And while going HTML 5, start migrating to HTML 5 layout.
> >
> > IE
> >
> > <div id="aside">
> > <aside>
> > // stuff
> > </aside>
> > </div>
> >
> > Most browsers do not recognize the HTML 5 layout tags yet, so you have
> > to wrap them in a div and attach the style to the div, but as browsers
> > start adopting HTML 5 your content will work with context features even
> > while still wrapped in the div tags.
> >
> > It is particularly useful for article and section, where the depth of a
> > section within an article can be helpful for non visual browsers.
>
> Just a word of thought... if you're doing styling... use classes and not
> IDs. Use of IDs for styling is very often indicative of inexperience,
> inability, or lack of understanding with respect to CSS.
>
> Cheers,
> Rob.
> --
> http://www.interjinn.com
> Application and Templating Framework for PHP
>
It would depend I think. I use ID's when I know that the element I'm
giving it to will be the only one on the page. Such as the header, main
navbar, footer, etc.
Thanks,
Ash
http://www.ashleysheridan.co.uk