Details
-
Type: Bug
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P01, 4.0.BETA
-
Fix Version/s: EE-3.3.0.GA_P02, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:HideICEfaces trunk rev# 36979 / 37828
EE-3.3.0.GA Maintenance Branch
Server: Tomcat7
Browser: all
Test app: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/dateTimeEntryShowICEfaces trunk rev# 36979 / 37828 EE-3.3.0.GA Maintenance Branch Server: Tomcat7 Browser: all Test app: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/dateTimeEntry
-
Assignee Priority:P2
Description
Component styling issues are visible in the ACE regression tests for ace:dateTimeEntry (FF23, IE10, Chrome29).
These issues cannot be reproduced in showcase.
1) when multiple dateTimeEntry pages are displayed (popup or inline component) - screen shot 1.png.
2) when the dateTimeEntry component is displayed inline for a single month (pages=1) - see attached 2.png.
Steps to reproduce:
- build and deploy the dateTimeEntry test application located here: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/dateTimeEntry
- issue1) can be reproduced by loading in any browser http://localhost:8080/dateTimeEntry/calendarAttribute.jsf and opening the popup calendar on the demo page, without changing any of the attributes.
- issue2) can be seen by loading in any browser: http://localhost:8080/dateTimeEntry/calendarOnly.jsf
Last revision number where both issues pass is trunk rev# 36978.
On rev# 36979 only issue 1) dateTimeEntry with multiple pages - fails; issue 2) passes.
On rev# 37062 both issues 1) and 2) fail, but the wrong styling is different from what it is now with the current revision #
These issues cannot be reproduced in showcase.
1) when multiple dateTimeEntry pages are displayed (popup or inline component) - screen shot 1.png.
2) when the dateTimeEntry component is displayed inline for a single month (pages=1) - see attached 2.png.
Steps to reproduce:
- build and deploy the dateTimeEntry test application located here: http://server.ice:8888/svn/repo/qa/trunk/Regression-Icefaces2/Sparkle/Nightly/dateTimeEntry
- issue1) can be reproduced by loading in any browser http://localhost:8080/dateTimeEntry/calendarAttribute.jsf and opening the popup calendar on the demo page, without changing any of the attributes.
- issue2) can be seen by loading in any browser: http://localhost:8080/dateTimeEntry/calendarOnly.jsf
Last revision number where both issues pass is trunk rev# 36978.
On rev# 36979 only issue 1) dateTimeEntry with multiple pages - fails; issue 2) passes.
On rev# 37062 both issues 1) and 2) fail, but the wrong styling is different from what it is now with the current revision #
Attaching before-after screenshot.
The cause of the first issue is that revision 36979 (
ICE-9143) introduced some localisation changes, and the weekdays went from being displayed as "Su Mo Tu We Th Fr Sa" to being displayed as "Sun Mon Tue Wed Thu Fri Sat", taking more width, while the width of the container remained the same, as seen in the before-after screenshot.This issue is easily fixed with custom app styling, but this is prone to change depending on the locale. The names of the week and other labels could take more or less space. Perhaps, we could programmatically set the width of the container, based on the width of its inner elements. We could make this behaviour configurable as well.
The second issue started at revision 37048, when the fixed width of the container was removed from the CSS file, making the calendar take as much space as possible. Again, this is easily fixed at the app level, and if can also be fixed with the approach described in the previous paragraph.