[jira] Resolved: (WICKET-2158) AutoComplete onfocus behavior only working on last autocomplete field
[
https://issues.apache.org/jira/browse/WICKET-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerolf Seitz resolved WICKET-2158.
--
Resolution: Fixed
Fix Version/s: 1.4.0
resolving this issue as fixed, as of revision 791516 (before the 1.4.0 release)
committed by jcompagner ("forgotton declaration of var objonfocus;")
> AutoComplete onfocus behavior only working on last autocomplete field
> -
>
> Key: WICKET-2158
> URL: https://issues.apache.org/jira/browse/WICKET-2158
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
>Affects Versions: 1.4-RC2
>Reporter: Peter Alfred Østergaard
> Fix For: 1.4.0
>
>
> 1.4rc2 wicket-autocomplete.js have some changes in onfocus behavior that seem
> to be working only for the last autocomplete field.
> It could be cause by a global "objonfocus" in Wicket.AutoComplete
> Initialiaze. The objonfocus seems to be missing in "pointers of the browser
> events".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1184) PageSavingThread keeps running after undeploy
[ https://issues.apache.org/jira/browse/WICKET-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-1184: -- Fix Version/s: (was: 1.3.1) > PageSavingThread keeps running after undeploy > - > > Key: WICKET-1184 > URL: https://issues.apache.org/jira/browse/WICKET-1184 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 1.3.0-rc1 > Environment: Glassfish v2 >Reporter: Francis De Brabandere > > We are deploying our wicket application to Glassfish (v2). After undeploying > and deploying a few times the PageSavingThread's of each deploy keeps > running. > I'm not having this problem when deploying the phonebook example (it does not > seem tot be triggering that thread) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2353) CLONE - bug: setObject(null) called for excplicitly invisible fields in a non-visible enclosure
[ https://issues.apache.org/jira/browse/WICKET-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-2353: -- Fix Version/s: (was: 1.3.3) > CLONE - bug: setObject(null) called for excplicitly > invisible fields in a non-visible enclosure > - > > Key: WICKET-2353 > URL: https://issues.apache.org/jira/browse/WICKET-2353 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 1.4-RC5, 1.4-RC6 >Reporter: Artur Wronski >Assignee: Igor Vaynberg > > The bug is still in 1.4-rc5 despite the fact that has status fixed in 1.3.3: > https://issues.apache.org/jira/browse/WICKET-1391 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2253) JavaScript null reference in IE7 for autocomplete text fields added by AJAX
[
https://issues.apache.org/jira/browse/WICKET-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-2253:
--
Fix Version/s: (was: 1.4-RC2)
(was: 1.3.6)
> JavaScript null reference in IE7 for autocomplete text fields added by AJAX
> ---
>
> Key: WICKET-2253
> URL: https://issues.apache.org/jira/browse/WICKET-2253
> Project: Wicket
> Issue Type: Bug
>Reporter: Per Cederberg
>
> IE7 displays an null reference error when adding a Wicket
> AutoCompleteTextField to a form as part of an AJAX response. This is caused
> by the INPUT DOM element not being immediately accessible, since it is added
> as HTML text (via innerHTML) instead of via the normal DOM API:s. So, the
> JavaScript autocomplete initialization code must be delayed until the HTML
> code has been parsed and properly inserted into the DOM tree.
> We've solved this by patching our local copy of Wicket 1.3.x in the
> wicket-autocomplete.js file:
> @@ -39,6 +37,7 @@
> var KEY_CTRL=17;
> var KEY_ALT=18;
>
> +var initCounter=10; // counter to avoid eternal init calls
> var selected=-1; // index of the currently selected item
> var elementCount=0; // number of items on the auto complete list
> var visible=0; // is the list visible
> @@ -63,6 +62,24 @@
> var throttleDelay = 300;
>
> function initialize(){
> +// Ugly hack to avoid null reference in IE7...
> +if (initCounter <= 0) {
> +return;
> +}
> +initCounter--;
> +var obj=wicketGet(elementId);
> +if (obj == null) {
> +setTimeout(initialize, 100);
> +return;
> +}
> +initCounter=0;
> +
> +// Avoid initializing same element twice
> +if (obj.wicketInit) {
> +return;
> +}
> +obj.wicketInit=true;
> This is not an optimal solution, but with the current Wicket solution of
> injecting HTML code as text into the DOM tree one is forced to poll for the
> inserted DOM node...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2484) CLONE -Improper HTML escaping for most wicket components and extensions
[ https://issues.apache.org/jira/browse/WICKET-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-2484: -- Fix Version/s: (was: 1.4-RC1) > CLONE -Improper HTML escaping for most wicket components and extensions > --- > > Key: WICKET-2484 > URL: https://issues.apache.org/jira/browse/WICKET-2484 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 1.3.0-final > Environment: Web Browser ... :-) >Reporter: Frank Klein Koerkamp >Assignee: Igor Vaynberg > > /*All text based components use a central function to escape html markup > probably contained in the text. > This is good style but the used method Strings.escapeMarkup() does not > fullfill its contract. > It does NOT escape all input but instead GUESSES and so it does not escape > the String "&#" because it assumes > an entity. > That means it is not possible to display data which looks like a numeric > entity. > This utility method should not guess about it's input but escape blindly. > If an entity should be "tunnelled through", there should be some kind of > attributation. > Using the current code it's not possible to have a text value of e.g. '' > getting properly stored and displayed > as exactly these 5 chars. > (Try it at http://wicketstuff.org/wicket13/compref/?wicket:interface=:0 > )*/ > This change is given us problems we often use ' ' in our propery files. > We use this to show a space or things like it. With updating to 1.4 we see > that the code is shown instead of the space. > If this is not fixed, how can we work around it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1864) MockHttpServletRequest does not support absolute redirection URLs.
[ https://issues.apache.org/jira/browse/WICKET-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-1864: -- Fix Version/s: (was: 1.3.8) (was: 1.4-RC2) > MockHttpServletRequest does not support absolute redirection URLs. > -- > > Key: WICKET-1864 > URL: https://issues.apache.org/jira/browse/WICKET-1864 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 1.4-M3 >Reporter: Maarten Billemont > Attachments: Wicket-Quickstart.zip > > > Using the sendRedirect(String) method on an MockHttpServletRequest object > causes bugged behaviour when the URL that is passed is absolute. > The following code needs to change (line 1277): > // We need to absolutize the redirect URL as we are not as > smart as a web-browser > // (WICKET-702) > url = getContextPath() + getServletPath() + "/" + redirect; > into, for example: > // We need to absolutize the redirect URL as we are not as > smart as a web-browser > // (WICKET-702) > url = redirect.charAt(0) == '/' ? redirect : redirect. > getContextPath() + getServletPath() + "/" + redirect; > After a few redirects I end up at: > /BankApplication/BankApplication//BankApplication > Which is not where I want to be. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1934) Hard coded size=8 attribute in DateTimeField.html is too small. DateField.html also has the same issue.
[ https://issues.apache.org/jira/browse/WICKET-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-1934: -- Fix Version/s: (was: 1.4-RC2) > Hard coded size=8 attribute in DateTimeField.html is too small. > DateField.html also has the same issue. > --- > > Key: WICKET-1934 > URL: https://issues.apache.org/jira/browse/WICKET-1934 > Project: Wicket > Issue Type: Bug > Components: wicket-datetime >Affects Versions: 1.4.3 > Environment: all >Reporter: Zsolt Rohberg >Assignee: Igor Vaynberg >Priority: Minor > > In the associated markup of DateTimeField the date input field has a hard > coded size=8 attribute. This is too small. At least 11 or more character > required for some locales (eg. the current date in hungarian: "2008.11.14."). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1802) Propertyresolver could be more informative
[ https://issues.apache.org/jira/browse/WICKET-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Vaynberg updated WICKET-1802: -- Fix Version/s: (was: 1.4-RC1) (was: 1.3.5) > Propertyresolver could be more informative > -- > > Key: WICKET-1802 > URL: https://issues.apache.org/jira/browse/WICKET-1802 > Project: Wicket > Issue Type: Improvement > Components: wicket >Affects Versions: 1.4-M3 >Reporter: Martin Makundi >Assignee: Johan Compagner > Original Estimate: 1h > Remaining Estimate: 1h > > WicketMessage: no set method defined for value: true on object: ... > at > org.apache.wicket.util.lang.PropertyResolver$MethodGetAndSet.setValue(PropertyResolver.java:1107) > In case there is a getter method defined, it would significantly help > debugging to display the get method name in the exception. > I suggest fixing the problem with: > - " on object: " + object); > + " on object: " + object + " while > respective getMethod being " + getMethod.getName()); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2592) Add support for arbitrary PageParameters values in QueryStringUrlCodingStrategy
[ https://issues.apache.org/jira/browse/WICKET-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Radchenko updated WICKET-2592: Attachment: QuertStringUrlCodingStrategyTest.java > Add support for arbitrary PageParameters values in > QueryStringUrlCodingStrategy > --- > > Key: WICKET-2592 > URL: https://issues.apache.org/jira/browse/WICKET-2592 > Project: Wicket > Issue Type: Improvement > Components: wicket >Affects Versions: 1.4.3 >Reporter: Marat Radchenko > Attachments: QuertStringUrlCodingStrategyTest.java > > > QueryStringUrlCodingStrategy, in contrast to > BookmarkablePageRequestTargetUrlCodingStrategy that it inherits from, > supports only String and String[] values. This makes it hard to switch > strategies. > Please, make it support arbitrary value type by calling toString() on them. > Testcase attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-2592) Add support for arbitrary PageParameters values in QueryStringUrlCodingStrategy
Add support for arbitrary PageParameters values in QueryStringUrlCodingStrategy --- Key: WICKET-2592 URL: https://issues.apache.org/jira/browse/WICKET-2592 Project: Wicket Issue Type: Improvement Components: wicket Affects Versions: 1.4.3 Reporter: Marat Radchenko Attachments: QuertStringUrlCodingStrategyTest.java QueryStringUrlCodingStrategy, in contrast to BookmarkablePageRequestTargetUrlCodingStrategy that it inherits from, supports only String and String[] values. This makes it hard to switch strategies. Please, make it support arbitrary value type by calling toString() on them. Testcase attached. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2591) Allow subclasses of AuthenticatedWebSession to set "signedIn" field
[ https://issues.apache.org/jira/browse/WICKET-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Radchenko updated WICKET-2591: Description: My app implements "remember me" service by setting cookie in authenticate method of custom session that subclasses AuthenticatedWebSession. In order to automatically login user if cookie present, i need to set "signedIn" field to true when session is created, however it isn't possible since "signedIn" is private and no way to set it is available. was: My app implements "remember me" service by setting cookie in authenticate method of custom session that subclasses AuthenticatedWebSession. However, in order to automatically login user if cookie present, i need to set "signedIn" field to true when session is created, however it isn't possible since "signedIn" is private and no way to set it is available. > Allow subclasses of AuthenticatedWebSession to set "signedIn" field > --- > > Key: WICKET-2591 > URL: https://issues.apache.org/jira/browse/WICKET-2591 > Project: Wicket > Issue Type: Improvement > Components: wicket-auth-roles >Affects Versions: 1.4.3 >Reporter: Marat Radchenko > > My app implements "remember me" service by setting cookie in authenticate > method of custom session that subclasses AuthenticatedWebSession. > In order to automatically login user if cookie present, i need to set > "signedIn" field to true when session is created, however it isn't possible > since "signedIn" is private and no way to set it is available. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-2591) Allow subclasses of AuthenticatedWebSession to set "signedIn" field
Allow subclasses of AuthenticatedWebSession to set "signedIn" field --- Key: WICKET-2591 URL: https://issues.apache.org/jira/browse/WICKET-2591 Project: Wicket Issue Type: Improvement Components: wicket-auth-roles Affects Versions: 1.4.3 Reporter: Marat Radchenko My app implements "remember me" service by setting cookie in authenticate method of custom session that subclasses AuthenticatedWebSession. However, in order to automatically login user if cookie present, i need to set "signedIn" field to true when session is created, however it isn't possible since "signedIn" is private and no way to set it is available. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
