Re: [WSG] Using CSS to select a tag having an ID attribute: page served as application/xhtml+xml

[Yuval Ararat]

Sorry for the double post, gmail/firefox are going mad.
in the sample code non of the tags carry the attribute name.

On Thu, Dec 17, 2009 at 11:14 PM, Grant Bailey <
grant_malcolm_bai...@westnet.com.au> wrote:

>  Yuval,
> I don't understand your message - did I miss something?
> Grant
>
>  -Original Message-
> *From:* li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] *On
> Behalf Of *Yuval Ararat
> *Sent:* Thursday, 17 December 2009 10:11 PM
> *To:* wsg@webstandardsgroup.org
> *Subject:* Re: [WSG] Using CSS to select a tag having an ID attribute:
> page served as application/xhtml+xml
>
> Am i the only one missing the name attribute in the samples?
>
> On Thu, Dec 17, 2009 at 8:00 PM, Grant Bailey <
> grant_malcolm_bai...@westnet.com.au> wrote:
>
>> Sorry everyone, I just discovered what the problem was:
>>
>> I have multiple style sheets and the browsers were only applying one,
>> not two as required, due to my misuse of the 'name' attribute of the
>> stylesheet instruction, as illustrated below.
>>
>> This was incorrect:
>>
>> > alternate="no" title="Default" media="screen, projection"?>
>> > alternate="no" title="Lesson" media="screen, projection"?>
>> > alternate="yes" title="Print" media="print"?>
>>
>> ... as the 'name' attribute must be the same for all stylesheets that
>> you want the browser to apply by default using the cascade. The
>> following fixed the problem:
>>
>> > alternate="no" title="Screen" media="screen, projection"?>
>> > alternate="no" title="Screen" media="screen, projection"?>
>> > alternate="yes" title="Print" media="print"?>
>>
>> As the 'title' attribute is optional you might be best leaving it out!
>>
>> Kind regards,
>>
>> Grant Bailey
>>
>>
>> -Original Message-
>> From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
>> On Behalf Of Grant Bailey
>> Sent: Thursday, 17 December 2009 7:41 PM
>> To: wsg@webstandardsgroup.org
>> Subject: [WSG] Using CSS to select a tag having an ID attribute: page
>> served as application/xhtml+xml
>>
>>
>> Hello,
>>
>> I've recently started serving my web pages as xml pages using the MIME
>> type application/xhtml+xml rather than text/css as previously. This
>> works fine as my pages were already xhtml compliant, with one exception:
>> my external CSS stylesheets are no longer honoured by any browser to the
>> extent that they select ID attributes.
>>
>> For example:
>>
>> [XHTML]
>> 
>>  Survival: the basics
>> 
>>
>> [CSS]
>> #div_Heading {
>> border: thin black solid;
>> }
>>
>> If I serve my page as text/css the border appears as expected but when
>> the page is served as application/xhtml+xml, no border is visible. There
>> is only one ID named div_Heading in the document and the document itself
>> validates.
>>
>> Could someone please advise me what might be going wrong as I have been
>> unable to find anything of assistance on the web or in the WSG forums.
>>
>> Many thanks and regards,
>>
>> Grant Bailey
>>
>>
>>
>>
>> ***
>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> Help: memberh...@webstandardsgroup.org
>> ***
>>
>>
>>
>>
>> ***
>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> Help: memberh...@webstandardsgroup.org
>> ***
>>
>>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] Using CSS to select a tag having an ID attribute: page served as application/xhtml+xml

[Yuval Ararat]

Am i the only one missing the name attribute in the samples?

On Thu, Dec 17, 2009 at 8:00 PM, Grant Bailey <
grant_malcolm_bai...@westnet.com.au> wrote:

> Sorry everyone, I just discovered what the problem was:
>
> I have multiple style sheets and the browsers were only applying one,
> not two as required, due to my misuse of the 'name' attribute of the
> stylesheet instruction, as illustrated below.
>
> This was incorrect:
>
>  alternate="no" title="Default" media="screen, projection"?>
>  alternate="no" title="Lesson" media="screen, projection"?>
>  alternate="yes" title="Print" media="print"?>
>
> ... as the 'name' attribute must be the same for all stylesheets that
> you want the browser to apply by default using the cascade. The
> following fixed the problem:
>
>  alternate="no" title="Screen" media="screen, projection"?>
>  alternate="no" title="Screen" media="screen, projection"?>
>  alternate="yes" title="Print" media="print"?>
>
> As the 'title' attribute is optional you might be best leaving it out!
>
> Kind regards,
>
> Grant Bailey
>
>
> -Original Message-
> From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
> On Behalf Of Grant Bailey
> Sent: Thursday, 17 December 2009 7:41 PM
> To: wsg@webstandardsgroup.org
> Subject: [WSG] Using CSS to select a tag having an ID attribute: page
> served as application/xhtml+xml
>
>
> Hello,
>
> I've recently started serving my web pages as xml pages using the MIME
> type application/xhtml+xml rather than text/css as previously. This
> works fine as my pages were already xhtml compliant, with one exception:
> my external CSS stylesheets are no longer honoured by any browser to the
> extent that they select ID attributes.
>
> For example:
>
> [XHTML]
> 
>  Survival: the basics
> 
>
> [CSS]
> #div_Heading {
> border: thin black solid;
> }
>
> If I serve my page as text/css the border appears as expected but when
> the page is served as application/xhtml+xml, no border is visible. There
> is only one ID named div_Heading in the document and the document itself
> validates.
>
> Could someone please advise me what might be going wrong as I have been
> unable to find anything of assistance on the web or in the WSG forums.
>
> Many thanks and regards,
>
> Grant Bailey
>
>
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>
>
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>
>


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] Google Wave webstandardsgroup?

[Yuval Ararat]

I have somemore invites to give.

yara...@googlewave.com

On Sat, Dec 5, 2009 at 5:51 AM, Duncan Hill  wrote:

> On Fri, 04 Dec 2009 16:04:52 -, Krystian Szastok 
> wrote:
>
>  I think it's a great idea.
>>
>> Problem is that wave is for group projects, so really, if we wanted to
>> roll it out we'd need to start creating some kind of community
>> projects I guess...
>>
>> But I do definitely want to participate.
>>
>> Thanks,
>> Krystian
>>
>>  I'm still just feeling my way in Wave, but it seems that it can be
> one-to-one as easily as it can group involvement.
>
> There is of course the risk that main-line topics get handled in a Wave and
> that could exclude any list members that have not signed up, or do not have
> the facility to use Wave.
> It would probably also not show up in the list archives and I know from
> personal experience that I have had many of my own queries answered with a
> simple archive search.
>
> Perhaps an idea to start is to add our 'Wave' address to our signature.
>
> Duncan
> dun...@googlewave.com
>
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>
>


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: More than one H1? (was [WSG] Out of Office AutoReply: WSG Digest)

[Yuval Ararat]

I am not sure that a page with multiple important subject does not exist. so
IA wise and semantic wise this is not a must. google wise it is.

On Fri, Oct 16, 2009 at 10:55 PM, Jason Grant  wrote:

> Tim,
> Well done for reading the spec - it's always a must.
>
> However, Google came after the HTML4.01 spec and what Google wants we give
> it - so the 'only one H1 per page' guideline comes from SEO best practices
> as well as general semantics and IA best practices.
>
> So the spec does not tell you to use one H1 per page, but the spec is not
> the be all and end all of guidelines.
>
> Thanks,
>
> Jason
>
> On Fri, Oct 16, 2009 at 12:32 PM, Tim White  wrote:
>
>> On Fri, Oct 16, 2009 at 4:23 AM, Marilyn Langfeld 
>> wrote:
>>
>>> ...
>>>
>>
>>
>>>  H1 is reserved for the title of the page. In a document, at least,
>>> there's only one title, while there may be many first level headings.
>>> ...
>>>
>>
>>
>>> So H1 is, IMHO, not the first level header, but the T1, or main title of
>>> the page. A logo is never, IMHO again, the title of the page.
>>>
>>
>>
>> Let's look at what the specification says;
>>
>> "A heading element briefly describes the topic of the section it
>> introduces. Heading information may be used by user agents, for example, to
>> construct a table of contents for a document automatically.
>>
>> There are six levels of headings in HTML with 
>> H1 as
>> the most important and 
>> H6 as
>> the least. Visual browsers usually render more important headings in larger
>> fonts than less important ones."
>>
>> http://www.w3.org/TR/html401/struct/global.html#h-7.5.5
>>
>> Nowhere does it say that H1s are for page titles or that there can be only
>> 1 per page. In fact, the example shows two being used.
>>
>> ~ Tim
>>
>> ***
>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> Help: memberh...@webstandardsgroup.org
>> ***
>>
>
>
>
> --
> Jason Grant BSc, MSc
> CEO, Flexewebs Ltd.
> www.flexewebs.com
> ja...@flexewebs.com
> +44 (0)7748 591 770
> Company no.: 5587469
>
> www.flexewebs.com/semantix
> www.twitter.com/flexewebs
> www.linkedin.com/in/flexewebs
>
> ***
>
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: More than one H1? (was [WSG] Out of Office AutoReply: WSG Digest)

[Yuval Ararat]

The issue with having more then 1 H! tag is not the validity of the page as
XHTML or HTML5 or any other specification, its not even affecting WCAG1/2.
the only case that is affected is the search engines relationship with H1
that entitled it as the Content's Title. it is not mandatory that it will be
the same as the Title tag but it should be relevant to the Content and a
page is better off with only 1 H1 for search engines.

On Fri, Oct 16, 2009 at 10:32 PM, Tim White  wrote:

> On Fri, Oct 16, 2009 at 4:23 AM, Marilyn Langfeld 
> wrote:
>
>> ...
>>
>
>
>> H1 is reserved for the title of the page. In a document, at least, there's
>> only one title, while there may be many first level headings.
>> ...
>>
>
>
>> So H1 is, IMHO, not the first level header, but the T1, or main title of
>> the page. A logo is never, IMHO again, the title of the page.
>>
>
>
> Let's look at what the specification says;
>
> "A heading element briefly describes the topic of the section it
> introduces. Heading information may be used by user agents, for example, to
> construct a table of contents for a document automatically.
>
> There are six levels of headings in HTML with 
> H1 as
> the most important and 
> H6 as
> the least. Visual browsers usually render more important headings in larger
> fonts than less important ones."
>
> http://www.w3.org/TR/html401/struct/global.html#h-7.5.5
>
> Nowhere does it say that H1s are for page titles or that there can be only
> 1 per page. In fact, the example shows two being used.
>
> ~ Tim
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***
>


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

Re: [WSG] Out of Office AutoReply: WSG Digest

[Yuval Ararat]

Its not specified any where that a single H1 is the right approach. SEO guys
have found that google search engine tends to read the H1 as the main
subject and decided to punish any page with more then one. the punishment is
not severe so not every one of the major sites obey.
In HTML 5 there is a huge discussion about the header
tagand the
existance of h1 inside of it. my take is that this will not catch
and only google and bing indexing will set the way they want to structure of
pages to be.


On Fri, Oct 16, 2009 at 3:45 PM,  wrote:

> Hi all, have come across something that I'm sure has come up before...
>
> Have created a new site with the logo wrapped in a H1 tag.
>
> The title of each page is also a H1.
>
> Just got word back from an outsourced SEO expert who says it's probably
> better if there was only one H1 on each page.
>
> Does anyone know of any online resources backing up this theory?
>
> I don't think it's a huge SEO concern at all but the signature on my return
> email doesn't have "SEO expert" on it.
>
> Many thanks.
>
>
>
> Christian Fagan
> Fagan Design
> fagandesign.com.au
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: memberh...@webstandardsgroup.org
> ***


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***