W3C home > Mailing lists > Public > www-style@w3.org > April 2005

Re: "Replacedness" of form-type elements

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 27 Apr 2005 12:13:47 +0000 (UTC)
To: Staffan Mhln <staffan.mahlen@comhem.se>
Cc: www-style@w3.org
Message-ID: <Pine.LNX.4.61.0504271212090.9723@dhalsim.dreamhost.com>
On Wed, 27 Apr 2005, Staffan Mhln wrote:
> >
> > CSS2.1 does not define which properties apply to form controls and 
> > frames, or how CSS can be used to style them. User agents may apply 
> > CSS properties to these elements. Authors are recommended to treat 
> > such support as experimental. A future level of CSS may specify this 
> > further.
> I would very much appreciate if you could elaborate a bit on the 
> intentions here?

It hasn't really been examined yet. Defining how form controls interact 
with the CSS model is a massive job.

> My orginal intentions with the question was otherwise more how this type 
> of element interacts with the inline model. Two UAs from three tested 
> seem to have a particular way of handling form-type elements baselines 
> and/or vertical-align, and their interpretation often makes sense but 
> their implementations seem to cause problems for the inline model. Are 
> there any UAs that implement 'inline-block' to this level of detail 
> (assuming that is a probable future solution)?

'inline-block' was poorly implemented by all UAs last time I tested it, 
but yes, one idea is to make some control (e.g. <input type="text">) into 
inline-blocks that are baseline-aligned.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 27 April 2005 12:13:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:18 UTC