Hi Mike,
I had a similar problem long time ago, I'm not sure, but I think you have
two options to solve this:
- One is adding* !important* (in order to overwrite the custom css for
the datePicker) to your css rules.
- The other one is create your custom * DatePickerStyle.css *and add
I generally copy the whole theme and make my changes to the css files.
Then in the module inherit my copied theme instead of the GWT theme.
This way the user does not have to load 2 different copies of any modified
CSS rules.
On Monday, April 23, 2012 9:03:15 PM UTC-4, Mike Dee wrote:
How
I agree, my first solution is quicker and easier but less efficient. My
second solution is the same as Patrick said, but Patrick has explained much
more better.
It's up to you.
Thx @Patrick for the clarification.
2012/4/24 Patrick Tucker tucker...@gmail.com
I generally copy the whole theme
Adolfo Panizo Touzon said:
... I think you have two options to solve this:
- One is adding* !important* (in order to overwrite the custom
css for the datePicker) to your css rules.
- The other one is create your custom * DatePickerStyle.css *and
add it to your DatePicker
But the question remains, why doesn't changing the gwt-DateBox CSS affect
the appearance of the DatabBox? In my case, the standard.css was replaced
with my own. So, why aren't my changes having any effect?
--
You received this message because you are subscribed to the Google Groups
Google
If you get a chance send out a screenshot of the computed style and regular
style after inspecting the input element in your dev console (firebug or
chrome dev tool, to the right of your previous screenshot).
There you can also in real time modify the element css property to get a
feel for what
