RichFaces 3.3.2.GA - default stylesheets changed?

[magiccreative]

hi,

just updated to the newest version (RichFaces 3.3.2.GA ). At first glance our application looks differently :).

What I noticed untill now is that suddenly tables are out of there place. The reason for that is new "default" padding I guess. Solved this by modifying .rich-table-cell and adding padding: 0px;.

A bigger problem is with calender. After the upgrade in the footer is shown the chosen date. That makes the calender get wider every time a date is selected. Looks bad, so how can I say do not show the chosen day in the footer. There is the showFooter property, but not showDateInFooter property to set to false :).

Thanks

[ilya_shaikovsky]

What I noticed untill now is that suddenly tables are out of there place. The reason for that is new "default" padding I guess. Solved this by modifying .rich-table-cell and adding padding: 0px;.

could you add some screenshot or maybe clarigy additionally. not sure that get an issue.

calendar - probably you specified width of calendar popup and it's smaller than the width of calendar with choosen date. I reproduced it on livedemo and solved the problem by removing the width or specifying larger one.

[magiccreative]

Here are the images for the calender problem. As you can notice, after a date is selected the calender width gets bigger. The reason for this are all the buttons and info in the footer. The difference from the previous version is that now in the footer one can also see the chosen date. But in my case I do not need to see it. Is there a way not to show chosen date in the footer?

Before date select:
http://twitpic.com/kt669



After:
http://twitpic.com/kt689


In the meantime I have solved that problem by changing "Übernehmen" to "OK" and "Löschen" to "x". Anyways it will be nice to be able to remove chosen things from the footer , like selected date, today button, or delete...

[ilya_shaikovsky]

confirmed. will be investigated. Will update you there.

[ilya_shaikovsky]

https://jira.jboss.org/jira/browse/RF-7967

yes, it's caused by missed parameter after optimization. Thanks for the report!