You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Gerolf Seitz (JIRA)" <ji...@apache.org> on 2007/12/19 22:06:44 UTC

[jira] Resolved: (WICKET-1236) DatePicker wrong positioning

     [ https://issues.apache.org/jira/browse/WICKET-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerolf Seitz resolved WICKET-1236.
----------------------------------

    Resolution: Fixed

fixed, form now on, also the scroll offset is taken into account when the datepicker is positioned.
i tested it with FF2.0.0.11, IE6, IE7, Opera 9.2.3 under Windows XP

can somebody with a mac test it too with the provided quickstart and trunk?

> DatePicker wrong positioning
> ----------------------------
>
>                 Key: WICKET-1236
>                 URL: https://issues.apache.org/jira/browse/WICKET-1236
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-datetime
>    Affects Versions: 1.3.0-rc1, 1.3.0-rc2
>            Reporter: Ilya German
>            Assignee: Gerolf Seitz
>         Attachments: datepicker-positioning-bug.zip
>
>
> Adding a DateField component to a WebPage and putting it low enough to be out of screen (so that one has to scroll down to reach the DateField-related icon) makes related DatePicker to show in a wrong position (apparently, some fixed vertical position, which could appear out of the visible screen at all)
> The problem goes away if I use calendar.js, DatePicker.js and wicket-date.js files from 1.3.0-beta3.
> Included is a testcase, somewhat it works only in Firefox, Opera throws the following error in javascript console (this problem also goes away if I switch to wicket-datetime-1.3.0-beta3.jar):
> script thread
> Error:
> name: TypeError
> message: Statement on line 63: Type mismatch (usually a non-object value used where an object is required)
> Backtrace:
>   Line 63 of inline#1 script in http://localhost:8080/datepicker/app/
>     Wicket.DateTime.init({widgetId : "date1", componentId : "date1", calendarInit : {WEEKDAYS_MEDIUM : ["Sun", "Mon", "Tue", "Wed", "Thu", "Fri", "Sat"], WEEKDAYS_1CHAR : ["S", "M", "T", "W", "T", "F", "S"], MONTHS_LONG : ["January", "February", "March", "April", "May", "June", "July", "August", "September", "October", "November", "December"], WEEKDAYS_LONG : ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"], MONTHS_SHORT : ["Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"], title : "&nbsp;", close : true, WEEKDAYS_SHORT : ["Su", "Mo", "Tu", "We", "Th", "Fr", "Sa"]}, datePattern : "dd/MM/yy", alignWithIcon : true, enableMonthYearSelection : false, fireChangeEvent : true, hideOnSelect : true});
>   Line 46 of inline#1 script in http://localhost:8080/datepicker/app/
>     initdate1DpJs();
>   Line 1316 of linked script http://localhost:8080/datepicker/app/resources/org.apache.wicket.extensions.yui.YuiLib/yuiloader-beta.js
>     this.onLoadComplete(this);
>   Line 1296 of linked script http://localhost:8080/datepicker/app/resources/org.apache.wicket.extensions.yui.YuiLib/yuiloader-beta.js
>     self.loadNext(name);
>   Line 22 of inline#1 script in http://localhost:8080/datepicker/app/
>     loaderCallback();
>   Line 1297 of linked script http://localhost:8080/datepicker/app/resources/org.apache.wicket.extensions.yui.YuiLib/yuiloader-beta.js
>     m.verifier(name, (function ()
> {
>   self.loadNext(name);
> }
> ));
>   Line 375 of linked script http://localhost:8080/datepicker/app/resources/org.apache.wicket.extensions.yui.YuiLib/yuiloader-beta.js
>     YUI.loaders[i].loadNext(mname);
>   Line 154 of linked script http://localhost:8080/datepicker/app/resources/org.apache.wicket.extensions.yui.YuiLib/yahoo/yahoo.js
>     ls[i](m);
>   Line 4951 of linked script http://localhost:8080/datepicker/app/resources/org.apache.wicket.extensions.yui.YuiLib/calendar/calendar.js
>     YAHOO.register("calendar", YAHOO.widget.Calendar, {version : "2.3.0", build : "442"});

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.