But, CSS changes presentation - displaying something as "block" doesn't
stop it being an inline element, just it's presentation.



On Fri, May 30, 2008 11:18 pm, Adam Martin wrote:
> img is only an inline element by default. Some simple css fixes that. An
> inline element does not have to be contained in a block level element at
> all!
>
> img {
> display: block
> }
>
> Kroon.Kurtis wrote:
>>> I'm not top-posting
>>>
>>
>> -----Original Message-----
>> From: Miscellaneous
>> Subject: Re: [WSG] Marking up company logo
>>
>> ... not be using a p tag [to] hold the logo --Adam
>> ... A <p> tag is supposed to hold a paragraph of text.  If it is only
>> holding an image, then there is no need for the surrounding <p> tag.
>> --Matt
>> ... see what www.alistapart.com is now using --Roxanne
>> ... beginning to think [a plain] html image tag would be better suited
>> to mark-up a company logo --Chris
>> ... I already blogged that. --Jason
>> ... only the homepage should have the company name/logo as the h1. As
>> you move through the site, the h1 should shift to the more specific top
>> heading on the page - on a category/index page it would be that
>> category's name; on a specific content page it should be the headline on
>> the content. --Ben
>> ... fwiw, I don't see it that way. A web site is not a book, there is no
>> cover. People can visit pages in a site without ever going through the
>> home page. --Thierry
>>
>> ... etc.
>>
>>
>> I'm surprised that no one has mentioned this ... but <img> is an inline
>> element.
>>
>> So, it has to be contained in a block-level element, like p, h#, div,
>> etc.
>>
>> Kurtis Kroon
>> Franchise Tax Board
>> State of California
>> 916-845-5603
>>
>> __________________________________________________________________________________________________
>>
>> CONFIDENTIALITY NOTICE: This email from the State of California is for
>> the sole use of the intended recipient and may contain confidential and
>> privileged information.  Any unauthorized review or use, including
>> disclosure or distribution, is prohibited.  If you are not the intended
>> recipient, please contact the sender and destroy all copies of this
>> email.
>>
>>
>>
>> *******************************************************************
>> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
>> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
>> Help: [EMAIL PROTECTED]
>> *******************************************************************
>>
>>
>>
>
>
> *******************************************************************
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
> Help: [EMAIL PROTECTED]
> *******************************************************************
>
>




*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to