When you're creating a component to existing web-site it is quite likely someone has used the "content" class name. Therefore his CSS will merge with your ".gwt-DisclosurePanel .content". There seem to be a naming convention in GWT. This just shows that there's a good reason to have one.
On Wed, Sep 8, 2010 at 2:43 AM, lineman78 <[email protected]> wrote: > It is because content and header all both children of the gwt- > DisclosurePanel class and they expect you to use child selectors. > Here is what they expect you use so that you don't end up with > collisions: > > .gwt-DisclosurePanel .content { > border: 2px solid black; > } > > On Sep 5, 11:08 am, Jaroslav Záruba <[email protected]> wrote: > > Hello > > > > There is one quite unfortunate class-name in the DisclosurePanel DOM. The > > widget serving for content gets class-name "content" assigned. Such > generic > > name is very collision prone, which situation I'm currently facing. > > Is there any special reason why this element did not get gwt-prefixed > > class-name as the rest has? > > > > Regards > > J. Záruba > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
