This is fair enough. But should we use class or id? Some forms could potentially have two edit boxes. And maybe something a little shorter like "box" instead of "bweditpageform" :)
I'll try and put something in the next release. All large text boxes should have the same class, I think. Cheers Dan On Wed, Feb 25, 2009 at 12:50 PM, jacmgr <[email protected]> wrote: > > For my sites, at first I modified the edit action and added an ID to > the textarea box. I think I called it id="bwtextarea"> and added a > line in my css for #bwtextarea. But I noticed that impacted on how > the core handles the GUI plugin. > > So instead I gave the FORM tag an id="bweditpageform" and then in css > I put #bweditpageform textarea {height: 600px; width: 450px} > > So on a skin without that css, the textbox appears as default sizes in > BW, but on a skin with that css it does seem to follow the css. > > So if the default action pages incorporated a an id into the form, > anyone could modify their css for their own need. > > john > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
