Re: CSS Property http://docs.webplatform.org/wiki/css/selectors/type

I suggest that page also needs one-line summaries of each item to
consolidate most of the info readers need, so they don't have to click
through for details of each.

Also, would prefer selectors that require an argument be listed with
parens, such as :nth-of-type() and :not().

Popular Class, ID, and Type (element) selectors should probably be grouped
together at the top.

--Mike S


On Tue, Jun 18, 2013 at 10:09 AM, Chris Mills <cmills@w3.org> wrote:

> David is right - this is a bit poor, and full of archaic language that
> will confuse beginners. "type selector" is the official name as per the
> spec (see http://www.w3.org/TR/selectors/), but a lot of people just call
> this an element selector, and I think that is a bit more intuitive. It
> basically just selects any element of the type (name) specified in place of
> E
>
> I think David's edit suggestions sound pretty reasonable. But make sure
> you keep in the "type selector" terminology somewhere too, as that is the
> official one.
>
> Chris Mills
> Opera Software, dev.opera.com
> W3C Fellow, web education and webplatform.org
> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
>
> On 17 Jun 2013, at 18:44, Scott Rowe <scottrowe@google.com> wrote:
>
> > Hi David,
> >
> > Thanks for looking into this. Obviously we need some work on our CSS
> selectors story. And when you come up with issues like this, be sure to
> address them to the entire community via public-webplatform@w3.org.
> >
> > I am not familiar with the design direction for the CSS selectors, and I
> share your impressions and confusions here.
> >
> > Can anyone address David's concerns?
> >
> > ~Scott
> >
> >
> >
> > On Sat, Jun 15, 2013 at 11:46 PM, David R. Herz <WPD@theherzes.com>
> wrote:
> > Dear Scott:
> >
> >
> >
> > I was just trying to get some basic syntax down and have come to a page
> the language of which confuses me.  As you were the major editor, I address
> this to you.
> >
> >
> >
> > On the page http://docs.webplatform.org/wiki/css/selectors, is the
> following:
> >
> >
> >
> > CSS Selector Reference (secondary heading)
> >
> > Type Selector (tertiary heading)
> >
> > elementname (bulleted item linking to another page)
> >
> >
> >
> > When I follow the link, I end up on
> http://docs.webplatform.org/wiki/css/selectors/type.
> >
> >
> >
> > While I am not clear what a “type” is other than just a specific element
> name, the syntax as set forth there does not match the example, or if it
> does, it has taken some logical steps which are mysterious to me.
> >
> >
> >
> > The language there is:
> >
> >
> >
> > Syntax
> >
> > <strong/>E <em/> {...}
> >
> >
> >
> > Parameters
> >
> > E
> >
> > String that specifies the name of a document language element type.
> >
> >
> >
> > While in the edit window, this shows up in the import notes section
> (i.e. potentially spurious unattended to stuff), to a casual visitor of the
> page, it seems off.  Do these notes represent some magic which a first
> level coder would be unaware of, or is this simply gibberish.  If the
> latter, I’d be happy to go ahead and fix it to:
> >
> >
> >
> > Syntax
> >
> >
> >
> >                                 elementname {property:parameter; . . . }
> >
> >
> >
> > where elementname is to be replaced by any html element (such as the H1
> in the example above), with any properties to be styled for that element
> placed within the curly brackets in the form property (such as “color” in
> the above example), followed by a colon, a valid value (teal), and a
> semicolon.
> >
> >
> >
> > So should I go ahead or did I miss something here?
> >
> >
> >
> > David R. Herz
> >
> > wpd@theherzes.com
> >
> >
> >
> >
>
>
>