I wanted to get my paragraphs to indent on a site so I tried the most
intuitive thing:
p:first-line{padding:1em}
It did nothing. I tested a couple other things to make sure I was doing
the right thing, but it appears that I can only change the font values.
Then I tried this:
G'day
I wanted to get my paragraphs to indent on a site so I tried the most
intuitive thing:
p:first-line{padding:1em}
How about
p { text-indent: 1em }
Regards
--
Bert Doorn, Better Web Design
http://www.betterwebdesign.com.au/
Fast-loading, user-friendly websites
Bert,
I wanted to get my paragraphs to indent on a site so I tried the most
intuitive thing:
p:first-line{padding:1em}
How about
p { text-indent: 1em }
This will indent the whole paragraph, while Alan is only trying to indent
the first line.
Thanks,
Tatham Oddie
Fuel Advance - Ignite
Tatham Oddie napisał(a):
How about
p { text-indent: 1em }
This will indent the whole paragraph, while Alan is only trying to indent
the first line.
According to the spec
(http://www.w3.org/TR/REC-CSS2/text.html#indentation-prop) it indents
only the first line:
This property specifies the
G'day
Lukasz Grabun wrote:
According to the spec
(http://www.w3.org/TR/REC-CSS2/text.html#indentation-prop) it indents
only the first line:
This property specifies the indentation of the first line of text in a
block.
So, the answer was and is correct.
Thanks Lukasz.
I tested my solution
Subject: Re: [WSG] Will HTML be nicer to PHP than XHTML?
Personally, I believe this is one of the strong argumens for XHTML. PHP is
very sloppy, and when you combine that with another sloppy language, HTML, the
mess is tremendos. For small projects and new people it's not much of an
issue,
I've started building a new template to get my main content section as
the first item in the source and solve some of my clearing problems.
Works great everywhere, except, now image this, Internet Deplorer. The
problem seems to be within either the nav or subnav lists that
follow one another.
I created a simple webpage containing a few paragraphs, a list and a table
(for tabular data). For some reason that I cannot for the life of me work
out, the font size of the text is much bigger in the table than elsewhere on
the page. (Tested in FF, Safari, Opera/mac). It's driving me nuts! I
You have an incomplete doctype which makes browsers go into quicks mode and
then font size inheritance is ignored inside a table.
Russ
I created a simple webpage containing a few paragraphs, a list and a table
(for tabular data). For some reason that I cannot for the life of me work
out, the
Thanks, Russ! I've fixed the doctype on the real page and it works
beautifully now.
The page is on a site with a non-web standards design that I've inherited.
It's due for a revamp in a couple of months when I plan to introduce
standards. I thought I'd start to experiment with this new page but
Scott Swabey (Lafinboy Productions) wrote:
I declare the height/width of textareas in CSS and don't use cols/rows in
the markup. I haven't come across any problems in [ limited ] testing so
far.
Unfortunately a textarea without rows and cols attributes won't pass
validation for xhtml 1.0
Patrick H. Lauke wrote:
I agree with the thread starter that the visual display size of a
textarea should really be defined via CSS. If these were maxrows and
maxcols, it would be a case for having it in the HTML, but as it stands
this seems to muddy the line a bit too much...
The need
Peter Asquith wrote:
The need for the rows and cols attributes can be seen once you imagine
the page without any CSS styling. Similarly, the requirement for the
size attribute on a text input element and width and height on img the
element.
Ultimately CSS may not be available on all the
Hi Cole,
Your mistake can also be step 3. If you're on a Windows box
then you're quite possibly dealing with conflicting image resolutions. If you
create a new image in Photoshop you'll notice that it's most likely set to
72dpi. I believe Windwos default is 80(?).
I then recommend using
On this note, does anyone know how to dynamically recreate all the other
image alignment options currently available through HTML? E.g. absmiddle,
text-top etc., or are we stuck with right/left and then margin settings?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Patrick H. Lauke wrote:
Personally, I find this type of answer quite dangerous, as it leads to a
slippery slope. Yes, the default rendering of browsers may be different
when CSS is not available, but does that mean we then still have to
stuff visual cues in HTML? The same rationale would
Hi Hope,
This was bugging me for ages too. I don't know _why_ it does it but my
workaround to-date has simply been to implicitly set font-size for p, td and
li. My table and list text usually display larger when I only set the
font-size in the body element.
I've asked this question before but is
On 7/4/05, Webmaster [EMAIL PROTECTED] wrote:
Hi Hope,
This was bugging me for ages too. I don't know _why_ it does it but my
workaround to-date has simply been to implicitly set font-size for p, td and
li. My table and list text usually display larger when I only set the
font-size in the
On 4/7/05 1:23 PM, Webmaster [EMAIL PROTECTED] wrote:
This was bugging me for ages too. I don't know _why_ it does it but my
workaround to-date has simply been to implicitly set font-size for p, td and
li. My table and list text usually display larger when I only set the
font-size in the body
Yes I had no idea that doctype could effect CSS rendering like this. I was
always scraed to use XHTML 1.0 strict but the combination below looks good.
It will become my new standard.
Thanks for asking the question.
Paul
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Wayne Godfrey wrote:
I've started building a new template to get my main content section as
the first item in the source and solve some of my clearing problems.
Works great everywhere, except, now image this, Internet Deplorer. The
problem seems to be within either the nav or subnav lists
Paul,
To switch to standards compliant mode, you must have a full and complete
doctype but it does NOT have to be XHTML at all.
Hope could just have easily changed from an incomplete HTML4.01 Transitional
doctype to a complete version. This is not a criticism of Hope, as she may
have had other
22 matches
Mail list logo
