Something that seems to work though I am not sure it is legal is to
add
textarea#myidvalue {height:auto}
after the blueprint css files have been included
On Jun 20, 11:07 am, ed <[email protected]> wrote:
> I have spent an inordinate amount of time trying to figure out why I
> could not set the number of rows and columns for a text area. Despite
> specifying rows= and cols= nothing seemed to work.
>
> Eventually it dawned on me to look at my CSS. There I notice that
> textareas should have a span-xx class defined, not sure I agree but I
> can live with that for now. However screen.css contains this
> specification
>
> screen.css:textarea {width:390px;height:250px;padding:5px;}
>
> Deleting the height specification caused the rows= to be honoured.
>
> I can think of no good reason why blueprint should dictate the
> *height* of input dialogues in a way that cannot be overriden using
> normal textarea declarations
>
> So I request that the above line of screen.css be amended to read
>
> screen.css:textarea {width:390px;padding:5px;}
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Blueprint CSS" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/blueprintcss?hl=en
-~----------~----~----~----~------~----~------~--~---
