Re: MaterialSearch - issues

2016-06-02 Thread Velusamy Velu
Great, will await its release. Thanks Sam V On Thursday, June 2, 2016 at 4:53:44 AM UTC-4, mark kevin ringor wrote: > > This is solved on 1.5.1 > > On Sunday, May 1, 2016 at 6:23:28 AM UTC+8, Velusamy Velu wrote: >> >> Hi Everyone - >> >> The GWT Material Design is a great contribution. I'm

Re: MaterialSearch - issues

2016-06-02 Thread mark kevin ringor
This is solved on 1.5.1 On Sunday, May 1, 2016 at 6:23:28 AM UTC+8, Velusamy Velu wrote: > > Hi Everyone - > > The GWT Material Design is a great contribution. I'm trying to use it in > our project (http://peruselab.com), we plan to release in Aug 2016. > > One of the component I'm trying to

Re: MaterialSearch - issues

2016-05-12 Thread Velusamy Velu
My fault, sorry for the inconvenience, I will make sure this doesn't happen again. On Wednesday, May 11, 2016 at 1:18:32 PM UTC-4, Mike Warne wrote: > > *** Did I post the issues in the wrong forum? *** > > Yes, this is probably the wrong forum. > GWT-MaterialDesign is not part of GWT. > >

Re: MaterialSearch - issues

2016-05-11 Thread Mike Warne
*** Did I post the issues in the wrong forum? *** Yes, this is probably the wrong forum. GWT-MaterialDesign is not part of GWT. https://gitter.im/GwtMaterialDesign/gwt-material MIke. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

Re: MaterialSearch - issues

2016-05-05 Thread Velusamy Velu
Solved it with a CSS style added to my application.css .input input[type=search]{ height: inherit !important; } This correction works as expected in Chrome, Opera, & FireFox. On Saturday, April 30, 2016 at 6:23:28 PM UTC-4, Velusamy Velu wrote: > > Hi Everyone - > > The GWT Material Design

Re: MaterialSearch - issues

2016-05-05 Thread Velusamy Velu
I'm wrong about Opera V36, the problem manifests in this browser too. I'm surprised seeing no response to my post. Did I post the issues in the wrong forum? Should I have reported this as a bug? If yes, can someone let me know where report this as a bug. Thanks Sam Velu On Saturday, April