facts, schmacts.

I guess we should consider updating it to match. Does anyone have a
sense of what ramifications this would hold? Should form.css add
margin and padding back in automatically?

chris

On Sep 1, 9:03 am, Tud <[EMAIL PROTECTED]> wrote:
> First line of Yahoo reset has "input" (resetting margin and padding)
> while Blueprint not
> Something I cannot understand, but I'm not a css expert, is:
> "textarea" is resetted and with a (Blueprint) style while "input" not
> ... we need to add a class
>
> Thanks
>
> Chris Eppstein ha detto: in data 1-09-2008 17:44:
>
> > Because Yahoo doesn't think it's necessary and they've thought long
> > and hard about this:
> >http://developer.yahoo.com/yui/reset/#code
>
> > You have to be very careful mucking with form input styling, many
> > style changes cause you to lose your native widgets which most people
> > consider to be a Bad Thing. You can have everything looking the same
> > in all browsers and platforms, but they might look equally bad...
>
> > If you need to reset your form elements, you'll need to do it
> > yourself. If you find there's some basic reset that works great at
> > solving the problem that you've not yet provided a concrete example
> > for, without losing native form controls, please feel free to show us
> > and maybe it'll become part of blueprint's reset.
>
> > Chris
>
> > On Sep 1, 8:21 am, davor <[EMAIL PROTECTED]> wrote:
>
> >> But still, why isn't there any input reset? It's bugging me now (doubt
> >> that all the UA render it same)
>
> >> On Mon, Sep 1, 2008 at 5:16 PM, Chris Eppstein <[EMAIL PROTECTED]> wrote:
>
> >>> You can always add a higher-precedence selector that changes whatever
> >>> styles blueprint provides. If you don't want the width just add:
>
> >>> body form input.text {width: auto;}
>
> >>> Chris
>
> >>> On Sep 1, 6:17 am, Tud <[EMAIL PROTECTED]> wrote:
>
> >>>> Hello Davor,
> >>>> I'd already seen the css classes but I don't like them because they have
> >>>> a fixed width
> >>>> I added the other settings for input to my css stylesheet but I don't
> >>>> understand why aren't there a reset and a default style for it
>
> >>>> Thanks
>
> >>>> davor ha detto: in data 1-09-2008 15:03:
>
> >>>>> Perhaps you should try using .text and .title classes on inputs?
>
> >>>>> But I'm not shure why the input isn't reseted or why isn't there 
> >>>>> default styles.
>
> >>>>> On Mon, Sep 1, 2008 at 2:56 PM, Tud <[EMAIL PROTECTED]> wrote:
>
> >>>>>> Hello,
>
> >>>>>> I'm developing a Ruby on Rails application using Blueprint but during
> >>>>>> testing it on different platforms and browsers I noticed that input
> >>>>>> fields were displayed in different ways (font, color, style,...). Than 
> >>>>>> I
> >>>>>> looked at Blueprint code and I found nor a reset neither a default 
> >>>>>> style
> >>>>>> for input fileds.
> >>>>>> why? Does a reason exist for this behavior I don't understand right 
> >>>>>> now?
>
> >>>>>> Thanks
>
> >> --
> >> "Meow" means "woof" in cat.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to