[
https://issues.apache.org/jira/browse/WICKET-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1005.
-
Resolution: Fixed
provide programmatic access to wicket-ajax.js
[
https://issues.apache.org/jira/browse/WICKET-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1011.
-
Resolution: Fixed
Fixed in 1.3.
wicketShow and wicketHide don't check for existence
[
https://issues.apache.org/jira/browse/WICKET-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp updated WICKET-1033:
Fix Version/s: (was: 1.3.0-beta5)
1.4.0-alpha
Postpoing as this should
[
https://issues.apache.org/jira/browse/WICKET-1087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539323
]
Matej Knopp commented on WICKET-1087:
-
I'm affraid there is nothing we can do. The issue is caused by firefox
that we don't alter the markup.
But we could expand all of them if needed. I don't mind to much
On 11/1/07, Matej Knopp [EMAIL PROTECTED] wrote:
Actually, I think that we might want to do this for all tags except
for couple of selected ones, e.g. hr /
This would also reduce confusion
It is semanticaly the same. And Firefox really treats div/ etc.
wrong way. Should we have a vote on this?
-Matej
On 11/1/07, Johan Compagner [EMAIL PROTECTED] wrote:
yeah we are generating extra attributes
but do we introduce tags itself ?
On 11/1/07, Matej Knopp [EMAIL PROTECTED] wrote
I'd say more like the enclosure should check is the component will
render rather than a simple isVisible check.
-Matej
On 11/1/07, Maurice Marrink [EMAIL PROTECTED] wrote:
On Oct 31, 2007 9:58 PM, Igor Vaynberg [EMAIL PROTECTED] wrote:
there seems to be a bit of a disconnect between render in
The modal window probably won't work well when paced in a page that is
loaded in iframe. Still, if you can provide a quickstart assigned to a
JIRA entry I will take a look if there is a quick fix for your
problem.
-Matej
On 11/1/07, Deepak Mahavishnu [EMAIL PROTECTED] wrote:
Hello!
I'm doing
I Zip the root project folder with all inside and attach it to a JIRA?
thanks,
f(t)
On 10/31/07, Matej Knopp [EMAIL PROTECTED] wrote:
Well, it's the last resort for you, but first resort for me :)
Issues that are easily reproduce (quickstart) can expect to be
resolved sooner, that's
Yourkit really works pretty darn well.
Btw. What wicket version are you using? And are you sure it's Wicket /
Web that is leaking?
-Matej
On 11/1/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
i use yourkit, it seems to work pretty darn well
-igor
On 11/1/07, Doug Leeper [EMAIL PROTECTED]
Why do you use frames anyway? If you want to pass things between
frames javascript is the only way, but I don't see what's the point of
using frames when you have framework capable of Ajax partial page
updates.
-Matej
On 11/1/07, Devin Venable [EMAIL PROTECTED] wrote:
I posted a question a few
Korbinian
Matej Knopp schrieb:
Korbinian Bachl wrote / napísal(a):
Hi,
Hi
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
content
. And we call
the replacement on a window.setTimeOut() on the specific page in which we
have the panel with subpanels.
thanks,
f(t)
On 10/30/07, Matej Knopp [EMAIL PROTECTED] wrote:
Sorry, I'm not sure I follow.
there is some code in replaceOuterHtml that seems redundant so it could
Override Page.configureResponse() and add the flags you want there.
-Matej
On 10/31/07, John Patterson [EMAIL PROTECTED] wrote:
Hi,
I notice that Pragma no-cache is set for every WebPage and I cannot
see how I can turn it off for my bookmarkable stateless pages could
would benefit from
.
I'll get right on it. Jira + QuickStart.
We must all contribute.
:-)
f(t)
On 10/31/07, Matej Knopp [EMAIL PROTECTED] wrote:
So even better than html page would be a quickstart attched to jira
issue that you create about this problem :-)
Cheers,
-Matej
On 10/31/07, Matej Knopp
Korbinian Bachl wrote / napísal(a):
Hi,
Hi
after creating yet another WebMarkupContainer to allow a ajaxified
resultset, i wondered why we are forced to this? - I mean, im not a JS
guru, but why do we have to create abstract containers to let some
content change?
You need to create
No idea. The javascript has nothing to do with wicket.
-Matej
On 10/30/07, Cristi Manole [EMAIL PROTECTED] wrote:
Hello,
I have a problem with ModalWindow.
No matter what I do I cannot manage to close it. Although the method for
closing it IS INDEED called (and then the focus set to the
of the sort.
If everything else fails I'll provide a QuickStart.
Thanks,
f(t)
On 10/23/07, Matej Knopp [EMAIL PROTECTED] wrote:
Can you provide a quickstart?
-Matej
On 10/23/07, Francisco Diaz Trepat - gmail
[EMAIL PROTECTED] wrote:
Hi. I'm going to try to explain the best that I can and without
Pen wrote / napísal(a):
I have a few question regarding the wicket usage. we are trying to Implement
wicket as our next MVC framework, Can please someone answer the questions
below
Hi
- about session support - wicket stores the render state of most renderer's
in session for different users
[
https://issues.apache.org/jira/browse/WICKET-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp closed WICKET-1059.
---
Resolution: Fixed
Remove onAttach
---
Key: WICKET-1059
It is already fixed in 1.3.
-Matej
On 10/29/07, wheleph [EMAIL PROTECTED] wrote:
Hello everyone!
I use Wicket 1.2.6 and when I try to disable AjaxSubmitLink via
link.setEnabled(false) call it really doesn't react on clicks but it still
looks like a regular link in browser. I mean that in
Looks like the FormComponentFeedbackBorder is not fixed yet. Will fix today.
-Matej
On 10/29/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
4) Pages are stateful now because of -
http://www.nabble.com/Stateless-page-creating-session-tf4604432.html#a13147396
Ah, I missed this. I fixed the
It is indeed a bug in FormComponentFeedbackBorder. Should be fixed
soon though :)
-Matej
On 10/29/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
in 1.3.0-beta4, Page.renderPage() doesn't call the updateFeedback() on its
children any more. Because of this change the FormComponentFeedbackBorder
I doubt it would prevent the page from being serialized. Versioning
doesn't spot all changes to page (e.g. setting a property) so we can't
rely on it, therefore we serialize it on every request.
However, if you really want to get around the serialization for certain
cases, you need to call
Are you sure that the newly added image has different src attribute
(e.g. adding a timestamp) than the old one? No-cache and no-store
headers on the image itself don't prevent the browser from caching
images on one page.
-Matej
Kirk Israel wrote / napísal(a):
I'm still having the
2007, at 17:27, Matej Knopp wrote:
I doubt it would prevent the page from being serialized. Versioning
doesn't spot all changes to page (e.g. setting a property) so we can't
rely on it, therefore we serialize it on every request.
However, if you really want to get around the serialization
requests.
-Matej
Eelco Hillenius wrote / napísal(a):
On 10/29/07, Matej Knopp [EMAIL PROTECTED] wrote:
I doubt it would prevent the page from being serialized. Versioning
doesn't spot all changes to page (e.g. setting a property) so we can't
rely on it, therefore we serialize it on every request
[
https://issues.apache.org/jira/browse/WICKET-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-1105:
---
Assignee: Matej Knopp
Missing javascript header referencies in Wicket portlet
[
https://issues.apache.org/jira/browse/WICKET-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538123
]
Matej Knopp commented on WICKET-1105:
-
The second markup file was missing both the head and body tags. Wicket
[
https://issues.apache.org/jira/browse/WICKET-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-1101:
---
Assignee: Matej Knopp
NullPointerException in HybridUrlCodingStrategy
[
https://issues.apache.org/jira/browse/WICKET-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537646
]
Matej Knopp commented on WICKET-1101:
-
This is kinda weird, can you please create a quickstart? I'll look
-8, and I am not well versed in this
technology to know how to do the encoding myself.
For now I am just creating my own IHeaderContribute to output a
script tag with the charset, but was wondering if there was any other
way.
On 25 Oct 2007, at 7:50 AM, Matej Knopp wrote:
Why do you want
Where do you have your LoadableDetachableModel declared? And what kind
of IDataProvider are you talking about? If it is wicket's
IDataProvider than it has to be serializable, because DataView/Table
keep it's reference.
LoadableDetachableModel is usually declared as anonymous class inside
It's about how you implement the TreeModel. You need to roll your own
TreeNode implementation that loads the children lazily when then
children() method is called. That way you don't have to populate the
whole tree upfront.
-Matej
On 10/25/07, lubosp [EMAIL PROTECTED] wrote:
I use extensions
you can try to add cache-control: no-store header to your page. If
that doesn't help, fill a jira issue with attached quickstart.
-Matej
On 10/25/07, Evan Chooly [EMAIL PROTECTED] wrote:
I'm having issues using the ALLP and the back button. I'm getting the
following error:
Wicket doesn't track dirty components (because there are lot of
different ways you can consider a component dirty). But you can mark
your dirty dirty yourself (e.g. setting some flags) and then use a
visitor (MarkupContainer.visitChildren()) to find dirty components and
add them to
This sounds good to me. +1
-Matej
On 10/25/07, Ate Douma [EMAIL PROTECTED] wrote:
Eelco Hillenius wrote:
I suggest a three state init parameter (non-portlet / portlet / autodetect)
and 'autodetect' could be the default option.
That sounds like a good idea to me. Though I think an
You can call setRedirect(false) during the request in the onSubmit
handler, that should prevent wicket from redirecting in that
particular case.
-Matej
On 10/24/07, Chris Lintz [EMAIL PROTECTED] wrote:
Ok. Its a good thing.. I didnt know it was the default setting. I guess i
should thank
Hi, unfortunately the Tree class is not able to grow horizontally,
neither it is possible for it to have a horizontal scrollbar. If you
need this features, you have to use the new LinkTree (or it's
superclass BaseTree) from wicket 1.3.
-Matej
On 10/24/07, David Struck [EMAIL PROTECTED] wrote:
No, there shouldn't be as far as I know. This might be a regression
though, could you file a jira issue and attach a quickstart that
demonstrates the problem? Thanks.
-Matej
On 10/24/07, Thies Edeling [EMAIL PROTECTED] wrote:
Hi all,
For validation purposes I've added a class exending
Why do you want to append the charset attribute? Why do you need it?
AFAIK if the charset is ommited the browser should use document
charset for the javascript as well. I don't understand the usecase
here.
-Matej
On 10/24/07, kent lai [EMAIL PROTECTED] wrote:
Hmm, or maybe even subclassing does
I believe this is already fixed in trunk, so it will also be part of beta 5.
-Matej
On 10/24/07, marcus dickerhof [EMAIL PROTECTED] wrote:
Thanks for the reply, but does apply to all ajax features?
I am not using an Ajax Link explicitly.I add an AjaxEventBehavior to a radio
component.
Do
Problem is that AjaxRequestTarget only applies to one page. If you
want to update the outer page (assuming that you have another page
inside modal window, not a panel), the only way to do it is from
within WindowClosedCallback registered to modal window. So you have to
mark somehow dirty
What you want to accomplish needs a little bit more of javascript,
it's not a simple timeout. Problem is that you need to make sure that
after the timeout the mouse is still over the element. Anyway, you can
use AjaxEventBehavior.getAjaxCallDecorator() to return your own
decorater which decorates
Modal window doesn't keep the reference to the page. What prevents you
from keeping the reference inside the page creator instance if you
need to?
-Matej
On 10/23/07, Kirk Israel [EMAIL PROTECTED] wrote:
I looked at the JavaDoc and inspected the class, but couldn't find a
clear way of getting
PROTECTED] wrote:
On 10/1/07, Matej Knopp [EMAIL PROTECTED] wrote:
I don't think there's any harm in leaving it, the problem is that
there are known thread-synchronization issues and there is noone
willing to fix it :)
Johan doesn't want to?! :-)
I'm +0
[
https://issues.apache.org/jira/browse/WICKET-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reopened WICKET-1090:
-
The fix definitely doesn't seem right. There is reason why the raw input is
persisted across
[
https://issues.apache.org/jira/browse/WICKET-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536523
]
Matej Knopp commented on WICKET-1090:
-
Now this is rather a fundamental and I don't think it's right to change
[
https://issues.apache.org/jira/browse/WICKET-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536527
]
Matej Knopp commented on WICKET-1090:
-
As for the problem, I believe the Ajax link should call modelChanged
[
https://issues.apache.org/jira/browse/WICKET-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1060.
-
Resolution: Fixed
Allow component to a IComponentSource implementation that can reconstruct
[
https://issues.apache.org/jira/browse/WICKET-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536549
]
Matej Knopp commented on WICKET-1090:
-
Well, I don't see easy solution for preserving sumitted values _and_
Hold on, the raw input _must_ be preserved after rendering. Where else
would we keep invalid input? The code also doesn't make sense - there
is no reason why it shouldn't work, except when the page was submitted
before the render and the submit was not validated.
Am I missing something?
-Matej
On 10/21/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 10/21/07, Matej Knopp [EMAIL PROTECTED] wrote:
Hold on, the raw input _must_ be preserved after rendering. Where else
would we keep invalid input?
Why do we need to keep invalid input after rendering? Any such input
is already
there.
-Matej
On 10/21/07, Matej Knopp [EMAIL PROTECTED] wrote:
On 10/21/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 10/21/07, Matej Knopp [EMAIL PROTECTED] wrote:
Hold on, the raw input _must_ be preserved after rendering. Where else
would we keep invalid input?
Why do we need to keep
I don't know tbh. I believe the request body is encoded in UTF-8.
People usually use UTF-8, so no-one was complaining before. Can't you
just use UTF-8? It's much safer than latin1.
-Matej
On 10/20/07, Johan Compagner [EMAIL PROTECTED] wrote:
are you configuring wicket and you appserver
Johan?
-Matej
On 10/20/07, jan_bar [EMAIL PROTECTED] wrote:
Hi,
my question was probably unclear, I will try to post more details:
When I leave a page, let's say id=40, wicket gets request to render new page
id=41 but flash on previous page still lives and send request to wicket
(this is
Actually, this might be a good idea, given all browsers support
script.readState consistently, which I need to confirm first. Apart
from that, I don't see any problem with it so far.
-Matej
On 10/19/07, Alexei Sokolov [EMAIL PROTECTED] wrote:
Actually,
The following code seems to be working
Optimize memory usage
-
Key: WICKET-1084
URL: https://issues.apache.org/jira/browse/WICKET-1084
Project: Wicket
Issue Type: Improvement
Reporter: Matej Knopp
Fix For: 1.3.0-beta5
Look
[
https://issues.apache.org/jira/browse/WICKET-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1083.
-
Resolution: Fixed
Inform wicket-ajax whether the application is running in a portlet
: Improvement
Reporter: Matej Knopp
Assignee: Matej Knopp
Fix For: 1.3.0-beta5
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hi, we are experimenting a little with component data representation
right now in order to improve memory consumption, so the trunk might
be a little unstable though. But so far I am unable to reproduce your
exception.
Sorry for inconvenience.
-Matej
On 10/18/07, Rüdiger Schulz [EMAIL
Hi, what wicket version are you using and how do you re-invoke the
javascript on ajax update? if you are using wicket 1.3 the best way to
do invoke the javascript is using
IHeaderResponse.renderOnDomReadyJavascript (works on regular page
refresh and also on ajax update).
-Matej
On 10/18/07, Doug
You should make your component implement IHeaderContributor. Or your
behavior, depends on how you implement your menu. Then you don't have
to worry about AjaxRequestTarget.
-Matej
On 10/18/07, Doug Leeper [EMAIL PROTECTED] wrote:
I just found this.
With a AjaxRequestTarget, you can get the
Hi all,
I've commited bunch of memory optimization that significantly reduce
memory usage. On the pages I've tested it the consumption was reduced
by up to 40% (live objects size).
The downside is that the changes touches component internals and there
might be some issues with it, so if you spot
Well, that was a joint effort with Johan!
-Matej
On 10/18/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
I've commited bunch of memory optimization that significantly reduce
memory usage. On the pages I've tested it the consumption was reduced
by up to 40% (live objects size).
You rock!
This should be fixed already in the latest trunk.
-Matej
On 10/18/07, Rüdiger Schulz [EMAIL PROTECTED] wrote:
Hello Johan,
yes, this worked for me. Thanks a lot for such a quick fix!
However, I had to build with maven tests disabled. And there was an
error on some of my pages, where I use
Hi,
isn't there a better way to detect if applicaiton is being run inside
a portlat than checking for classes from portlet-api on classpath? If
someone puts portlet-api by accident to classpath, wicket thinks it's
running in portlet environment, which have certain consequences, e.g.
the rendering
.
Eelco
On 10/15/07, chickabee [EMAIL PROTECTED] wrote:
The page was mount using HybridUrlCodingStrategy
--thanks
Matej Knopp-2 wrote:
How did you mount the page?
-Matej
On 10/15/07, chickabee [EMAIL PROTECTED] wrote:
Hi Guys, It seems
using IComponentResolver as long as those are
visible?
- Juha
Juha Alatalo wrote:
https://issues.apache.org/jira/browse/WICKET-1077
- Juha
Matej Knopp wrote:
Please create a JIRA entry and assign the example to it.
Thanks.
-Matej
On 10/15/07, Juha Alatalo [EMAIL PROTECTED
developers are not going to admit that this is a problem.
Ari S.
- Original Message -
From: Matej Knopp [EMAIL PROTECTED]
To: users@wicket.apache.org
Sent: Wednesday, October 17, 2007 2:15 PM
Subject: Re: VisitChildren + IComponentResolver broken in beta 4?
It depends on when you
developers are not going to admit that this is a problem.
Ari S.
- Original Message -
From: Matej Knopp [EMAIL PROTECTED]
To: users@wicket.apache.org
Sent: Wednesday, October 17, 2007 2:15 PM
Subject: Re: VisitChildren + IComponentResolver broken in beta 4?
It depends
Well, tbh, I don't know either. I think it's supposed to handle a
failure such as server not responding right now. I know before It
handled even exceptions, but i guess it's better to just display the
error page as we would normally do (which is current behavior).
-Matej
On 10/16/07, Eelco
There's no way removing onAttach() could cause such problems, as it
was basically a noop. The onAttach() implementations were just empty.
And if you had your onAttach implementation, you should get a
compilation error as onAttach is now final.
Are you sure you have cleared your browser cache when
Okay, the problem here is that protlet support broke
CryptedUrlWebRequestCodingStrategy.
-Matej
On 10/16/07, Matej Knopp [EMAIL PROTECTED] wrote:
There's no way removing onAttach() could cause such problems, as it
was basically a noop. The onAttach() implementations were just empty
Well, there are still circumstances where it can be useful, e.g.
request timeout, or other http error.
-Matej
On 10/16/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 10/16/07, Matej Knopp [EMAIL PROTECTED] wrote:
Well, tbh, I don't know either. I think it's supposed to handle a
failure
But then you have to use custom javascript, because you want to both
update the tree and the right frame.
-Matej
On 10/16/07, Kevin Liu [EMAIL PROTECTED] wrote:
Thank Igor :-)
But if I wanna change the tree behavior, such as expanding the Node when
the node is clicked as the junction link
It should be resolved shortly.
-Matej
On 10/16/07, Brandon Fuller [EMAIL PROTECTED] wrote:
Discussed here:
http://www.nabble.com/Wicket-Beta4-and-Ajax-Links-tf4616750.html
--
View this message in context:
[
https://issues.apache.org/jira/browse/WICKET-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1072.
-
Resolution: Fixed
Fix Version/s: 1.3.0-beta5
Stateless pages bind to http session
[
https://issues.apache.org/jira/browse/WICKET-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534997
]
Matej Knopp commented on WICKET-1073:
-
This actually doesn't make sense.
this
final Component component
[
https://issues.apache.org/jira/browse/WICKET-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-1076:
---
Assignee: Johan Compagner
SubmitLink component does not render markup id
[
https://issues.apache.org/jira/browse/WICKET-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535003
]
Matej Knopp commented on WICKET-1077:
-
This doesn't seem to be a bug in Wicket. In fact, the bug
Please create a JIRA entry and assign the example to it.
Thanks.
-Matej
On 10/15/07, Juha Alatalo [EMAIL PROTECTED] wrote:
Hi,
If the components are added on the page using ComponentResolver,
visitChildren() method seems to be working incorrectly. Created
following example which works in
We mostly use jetty as embedded in the project itself. Then starting a
web application is as simple as starting any other java application.
Also debugging is much simpler. No need to configure remote debug
connection, not to mention that you need to configure separate ports
if you want to debug
Unless you submit a quickstart I can't really help with this.
-Matej
On 10/15/07, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Hmm changing it OnChangeAjaxBehavior, makes it stop working if using it
in conjuction with datepicker on safari and FF..
BTW, i am using an text
Well, I guess you can. Still you need to have tomcat installed,
whereas with jetty you only need a 300kb jar in project. Also as
stated above, you don't need JSP support (compiler, etc) so the
footprint is really small.
-Matej
On 10/15/07, Sam Hough [EMAIL PROTECTED] wrote:
Still can't see why
How did you mount the page?
-Matej
On 10/15/07, chickabee [EMAIL PROTECTED] wrote:
Hi Guys, It seems that wicket has the special meaning of a dot ( . ) in the
URL. Wicket expects anything after a dot to be a number and throws Number
format exception if it is not, Is there is a way to use
[
https://issues.apache.org/jira/browse/WICKET-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534686
]
Matej Knopp commented on WICKET-1047:
-
I believe that urlFor definitely should not escape the URL. As escaping
[
https://issues.apache.org/jira/browse/WICKET-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-1074:
---
Assignee: Matej Knopp
Image resource parameters fail to output in src attribute
[
https://issues.apache.org/jira/browse/WICKET-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534689
]
Matej Knopp commented on WICKET-1074:
-
Actually, this seems to be already fixed (Juergen's commit).
Image
[
https://issues.apache.org/jira/browse/WICKET-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1074.
-
Resolution: Fixed
Image resource parameters fail to output in src attribute
[
https://issues.apache.org/jira/browse/WICKET-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1047.
-
Resolution: Fixed
Amersand escaped twice for ResourceLink href
[
https://issues.apache.org/jira/browse/WICKET-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp updated WICKET-1074:
Fix Version/s: 1.3.0-beta5
Image resource parameters fail to output in src attribute
We might add this to Wicket, can you please open a RFE and attach the
appropriate classes?
Thanks..
-Matej
On 10/14/07, Kent Tong [EMAIL PROTECTED] wrote:
Jan Kriesten wrote:
might be, but it's a nice feature for just styling col-width and
col-alignment.
actually, this would be an
[
https://issues.apache.org/jira/browse/WICKET-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-1048:
---
Assignee: Matej Knopp
After refreshing component with ajax target.addComponent
[
https://issues.apache.org/jira/browse/WICKET-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534516
]
Matej Knopp commented on WICKET-1048:
-
I've tested this with latest trunk and can't reproduce the problem
[
https://issues.apache.org/jira/browse/WICKET-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-948:
--
Assignee: Matej Knopp
Links don't work after using browser's back button (Statefull page
[
https://issues.apache.org/jira/browse/WICKET-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534517
]
Matej Knopp commented on WICKET-948:
Looks like a weird serialization problem. Can you please post the whole
[
https://issues.apache.org/jira/browse/WICKET-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534518
]
Matej Knopp commented on WICKET-1014:
-
Removed setting focus from appendJavascript, as it was causing
[
https://issues.apache.org/jira/browse/WICKET-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp reassigned WICKET-1014:
---
Assignee: Matej Knopp
AjaxEditableChoiceLabel doesn't work in IE 6
[
https://issues.apache.org/jira/browse/WICKET-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matej Knopp resolved WICKET-1014.
-
Resolution: Fixed
Fix Version/s: 1.3.0-beta5
AjaxEditableChoiceLabel doesn't work in IE
901 - 1000 of 2371 matches
Mail list logo
