[jira] Created: (WICKET-3281) autolink doesn't work with relative paths in borders
autolink doesn't work with relative paths in borders Key: WICKET-3281 URL: https://issues.apache.org/jira/browse/WICKET-3281 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 1.4.14 Reporter: Anatoly Kupriyanov Take the navomatic wicket example and move the Page2.java and Page2.html into an another java-package - relative paths in the NavomaticBorder.html will be resolved incorrectly, they resolved against current page, but not against NavomaticBorder.html. So, I cannot use autolink functionality from bordes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3281) autolink doesn't work with relative paths in borders
[ https://issues.apache.org/jira/browse/WICKET-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly Kupriyanov updated WICKET-3281: --- Comment: was deleted (was: Unit test) autolink doesn't work with relative paths in borders Key: WICKET-3281 URL: https://issues.apache.org/jira/browse/WICKET-3281 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 1.4.14 Reporter: Anatoly Kupriyanov Attachments: wicketbug.tgz Take the navomatic wicket example and move the Page2.java and Page2.html into an another java-package - relative paths in the NavomaticBorder.html will be resolved incorrectly, they resolved against current page, but not against NavomaticBorder.html. So, I cannot use autolink functionality from bordes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3281) autolink doesn't work with relative paths in borders
[ https://issues.apache.org/jira/browse/WICKET-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anatoly Kupriyanov updated WICKET-3281: --- Attachment: wicketbug.tgz Unit test autolink doesn't work with relative paths in borders Key: WICKET-3281 URL: https://issues.apache.org/jira/browse/WICKET-3281 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 1.4.14 Reporter: Anatoly Kupriyanov Attachments: wicketbug.tgz Take the navomatic wicket example and move the Page2.java and Page2.html into an another java-package - relative paths in the NavomaticBorder.html will be resolved incorrectly, they resolved against current page, but not against NavomaticBorder.html. So, I cannot use autolink functionality from bordes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3281) autolink doesn't work with relative paths in borders
[ https://issues.apache.org/jira/browse/WICKET-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974712#action_12974712 ] Anatoly Kupriyanov commented on WICKET-3281: BTW, how to click autolink from a test case? autolink doesn't work with relative paths in borders Key: WICKET-3281 URL: https://issues.apache.org/jira/browse/WICKET-3281 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 1.4.14 Reporter: Anatoly Kupriyanov Attachments: wicketbug.tgz Take the navomatic wicket example and move the Page2.java and Page2.html into an another java-package - relative paths in the NavomaticBorder.html will be resolved incorrectly, they resolved against current page, but not against NavomaticBorder.html. So, I cannot use autolink functionality from bordes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-1964) Add IBehavior.isVisibilityAllowed(Component) or so
[ https://issues.apache.org/jira/browse/WICKET-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924308#action_12924308 ] Anatoly Kupriyanov commented on WICKET-1964: Google for it by make invisible if model object is null keywords http://apache-wicket.1842946.n4.nabble.com/make-invisible-if-model-object-is-null-td1874965.html Add IBehavior.isVisibilityAllowed(Component) or so -- Key: WICKET-1964 URL: https://issues.apache.org/jira/browse/WICKET-1964 Project: Wicket Issue Type: New Feature Components: wicket Reporter: Anatoly Kupriyanov Assignee: Igor Vaynberg Fix For: 1.5-M3 A behavior should able to control component's visibility. Discussion http://www.nabble.com/make-invisible-if-model-object-is-null-tt20769823.html explains useful usecase -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-1404) Investigate default focus support (on Page or RequestCycle)
[
https://issues.apache.org/jira/browse/WICKET-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922023#action_12922023
]
Anatoly Kupriyanov commented on WICKET-1404:
It's bad idea to set focus from the onload event. This event could occur after
a control is visible and a user starts edit the control - focus suddenly jumps
to another one.
I hate this - I open page, it still loading but login/password form already
rendered and while I'm typing a password, page finishes loading and focus
suddenly jumps to the login box, it could reveal my password.
Usually it's better to put getElementById(' + component.getMarkupId() +
').focus() right after form component.
Investigate default focus support (on Page or RequestCycle)
---
Key: WICKET-1404
URL: https://issues.apache.org/jira/browse/WICKET-1404
Project: Wicket
Issue Type: New Feature
Components: wicket
Affects Versions: 1.3.1
Reporter: James Carman
Priority: Minor
Fix For: 1.5-M3
Attachments: WICKET-1404.patch
We need something which gives a component the focus when the page loads.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-693) What to do with the wicket dtd?
[ https://issues.apache.org/jira/browse/WICKET-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12673863#action_12673863 ] Anatoly Kupriyanov commented on WICKET-693: --- This DTD defines only wicket:id and wicket:preview attributes, but doesn't define any wicket elements. Is it just not finished or am I missing something? Answering previous question, you need make a !DOCTYPE, which will point to the wicket-xhtml1.4-strict.dtd, but it will not work well while .dtd is not complete. Afair, in IDEA it's possible to name file as .xhtml, instead .html, it gives more strict validations. What to do with the wicket dtd? --- Key: WICKET-693 URL: https://issues.apache.org/jira/browse/WICKET-693 Project: Wicket Issue Type: Bug Components: site, wicket Reporter: Martijn Dashorst Assignee: Timo Rantalaiho Fix For: 1.3.6, 1.4-RC2 The current dtd is located at the wicket.sf.net site, and may not even work. We need to come up with a solution for the wicket dtd and fix this for the future: ./jdk-1.4/wicket/src/site/resources/DTD/wicket-1.0-xhtml11.dtd: SYSTEM http://wicket.sourceforge.net/DTD/wicket-xhtml1.dtd; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-1964) Add IBehavior.isVisibilityAllowed(Component) or so
Add IBehavior.isVisibilityAllowed(Component) or so -- Key: WICKET-1964 URL: https://issues.apache.org/jira/browse/WICKET-1964 Project: Wicket Issue Type: New Feature Components: wicket Reporter: Anatoly Kupriyanov Fix For: 1.4-RC2, 1.5-M1 A behavior should able to control component's visibility. Discussion http://www.nabble.com/make-invisible-if-model-object-is-null-tt20769823.html explains useful usecase -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
