[jira] [Commented] (WICKET-6470) If AjaxPagingNavigator is added before table, count is called twice

[ https://issues.apache.org/jira/browse/WICKET-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652499#comment-16652499 ] Jezza commented on WICKET-6470: --- Sadly, the IDataProvider interface does say anything about if it's going

[jira] [Commented] (WICKET-6536) Add generic to MarkupContainer#visitChildren

[ https://issues.apache.org/jira/browse/WICKET-6536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652457#comment-16652457 ] Jezza commented on WICKET-6536: --- The "problem" isn't that Class isn't Class, it's Java not being able to

[jira] [Commented] (WICKET-6558) Prevent package locks after commitRequest

[ https://issues.apache.org/jira/browse/WICKET-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652441#comment-16652441 ] Jezza commented on WICKET-6558: --- Are you sure that's the cause? All pages that the thread locked are

[jira] [Comment Edited] (WICKET-6558) Prevent package locks after commitRequest

[ https://issues.apache.org/jira/browse/WICKET-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652441#comment-16652441 ] Jezza edited comment on WICKET-6558 at 10/16/18 9:09 PM: - Are you sure that's

[jira] [Commented] (WICKET-6427) Fire an event once all ajax timers are registered

[ https://issues.apache.org/jira/browse/WICKET-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650864#comment-16650864 ] Jezza commented on WICKET-6427: --- I don't have the right to close this ticket. Can someone else? > Fire an

[jira] [Commented] (WICKET-6582) Ajax should prevent components on a different page from rendering on the current one.

[ https://issues.apache.org/jira/browse/WICKET-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597127#comment-16597127 ] Jezza commented on WICKET-6582: --- Ok, so as I was creating the quickstart, I discovered the issue. The

[jira] [Created] (WICKET-6582) Ajax should prevent components on a different page from rendering on the current one.

Jezza created WICKET-6582: - Summary: Ajax should prevent components on a different page from rendering on the current one. Key: WICKET-6582 URL: https://issues.apache.org/jira/browse/WICKET-6582 Project:

[jira] [Commented] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512760#comment-16512760 ] Jezza commented on WICKET-6561: --- Ah, makes sense if I think about it. I didn't know wicket that long ago,

[jira] [Commented] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512471#comment-16512471 ] Jezza commented on WICKET-6561: --- After a quick search, WICKET-3098 popped up. Interestingly, it's

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512327#comment-16512327 ] Jezza edited comment on WICKET-6561 at 6/14/18 11:18 AM: - I have thought of an

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512327#comment-16512327 ] Jezza edited comment on WICKET-6561 at 6/14/18 11:18 AM: - I have thought of an

[jira] [Commented] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512327#comment-16512327 ] Jezza commented on WICKET-6561: --- I have thought of an solution which isn't terrible. Introduce a

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508268#comment-16508268 ] Jezza edited comment on WICKET-6561 at 6/11/18 4:13 PM: *Ninja edit:* Yeah, I

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508268#comment-16508268 ] Jezza edited comment on WICKET-6561 at 6/11/18 4:13 PM: *Ninja edit:* Yeah, I

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508268#comment-16508268 ] Jezza edited comment on WICKET-6561 at 6/11/18 4:11 PM: *Ninja edit:* Yeah, I

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508268#comment-16508268 ] Jezza edited comment on WICKET-6561 at 6/11/18 4:09 PM: Ehh, one could

[jira] [Comment Edited] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508268#comment-16508268 ] Jezza edited comment on WICKET-6561 at 6/11/18 4:08 PM: Ehh, one could

[jira] [Commented] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508268#comment-16508268 ] Jezza commented on WICKET-6561: --- Ehh, one could imagine behaviours as "attributes" to a give node, and

[jira] [Commented] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

[ https://issues.apache.org/jira/browse/WICKET-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508240#comment-16508240 ] Jezza commented on WICKET-6561: --- I can go ahead and open a PR for it if no one has any issue with it. >

[jira] [Created] (WICKET-6561) Behaviours receive events regardless if they were rejected by the component.

Jezza created WICKET-6561: - Summary: Behaviours receive events regardless if they were rejected by the component. Key: WICKET-6561 URL: https://issues.apache.org/jira/browse/WICKET-6561 Project: Wicket

[jira] [Updated] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jezza updated WICKET-6550: -- Description: Application, Session, RequestCycle, and Component all have #setMetadata and #getMetadata

[jira] [Comment Edited] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444743#comment-16444743 ] Jezza edited comment on WICKET-6550 at 4/19/18 8:31 PM: In the commit message, I

[jira] [Commented] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444746#comment-16444746 ] Jezza commented on WICKET-6550: --- Or if that isn't the direction we want to go in, the current state still

[jira] [Commented] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444743#comment-16444743 ] Jezza commented on WICKET-6550: --- In the commit message, I said it could be extended. Something like this

[jira] [Commented] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16444728#comment-16444728 ] Jezza commented on WICKET-6550: --- [https://github.com/apache/wicket/pull/276] [^Test.java] shows what is

[jira] [Updated] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jezza updated WICKET-6550: -- Attachment: Test.java > Unify all metadata capable objects. > --- > >

[jira] [Updated] (WICKET-6550) Unify all metadata capable objects.

[ https://issues.apache.org/jira/browse/WICKET-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jezza updated WICKET-6550: -- Attachment: mock.txt > Unify all metadata capable objects. > --- > >

[jira] [Created] (WICKET-6550) Unify all metadata capable objects.

Jezza created WICKET-6550: - Summary: Unify all metadata capable objects. Key: WICKET-6550 URL: https://issues.apache.org/jira/browse/WICKET-6550 Project: Wicket Issue Type: Improvement

[jira] [Comment Edited] (WICKET-6456) Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update

[ https://issues.apache.org/jira/browse/WICKET-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139788#comment-16139788 ] Jezza edited comment on WICKET-6456 at 8/24/17 9:44 AM: Yeah, in hindsight, my

[jira] [Comment Edited] (WICKET-6456) Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update

[ https://issues.apache.org/jira/browse/WICKET-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139788#comment-16139788 ] Jezza edited comment on WICKET-6456 at 8/24/17 9:43 AM: Yeah, in hindsight, my

[jira] [Comment Edited] (WICKET-6456) Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update

[ https://issues.apache.org/jira/browse/WICKET-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139788#comment-16139788 ] Jezza edited comment on WICKET-6456 at 8/24/17 9:43 AM: Yeah, in hindsight, my

[jira] [Commented] (WICKET-6456) Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update

[ https://issues.apache.org/jira/browse/WICKET-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139788#comment-16139788 ] Jezza commented on WICKET-6456: --- Yeah, in hindsight, my entire problem was caused from a misunderstanding

[jira] [Commented] (WICKET-6456) Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update

[ https://issues.apache.org/jira/browse/WICKET-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139773#comment-16139773 ] Jezza commented on WICKET-6456: --- It makes sense not to render the children's header if the parent is

[jira] [Created] (WICKET-6456) Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update

Jezza created WICKET-6456: - Summary: Headers not rendered for components inside nested TransparentWebMarkupContainer on ajax update Key: WICKET-6456 URL: https://issues.apache.org/jira/browse/WICKET-6456

[jira] [Comment Edited] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103199#comment-16103199 ] Jezza edited comment on WICKET-6346 at 7/27/17 1:29 PM: Should this be added to

[jira] [Issue Comment Deleted] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jezza updated WICKET-6346: -- Comment: was deleted (was: I should probably also format it to match the rest of wicket's style.) > Add

[jira] [Comment Edited] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103199#comment-16103199 ] Jezza edited comment on WICKET-6346 at 7/27/17 1:28 PM: Should this be added to

[jira] [Commented] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103205#comment-16103205 ] Jezza commented on WICKET-6346: --- I should probably also format it to match the rest of wicket's style. >

[jira] [Issue Comment Deleted] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jezza updated WICKET-6346: -- Comment: was deleted (was: I implemented this about a month or two ago, so I'd be happy to clean it up and

[jira] [Updated] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jezza updated WICKET-6346: -- Attachment: ServerTiming.java > Add Server-Timing response header > - > >

[jira] [Commented] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103201#comment-16103201 ] Jezza commented on WICKET-6346: --- I implemented this about a month or two ago, so I'd be happy to clean it

[jira] [Commented] (WICKET-6346) Add Server-Timing response header

[ https://issues.apache.org/jira/browse/WICKET-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103199#comment-16103199 ] Jezza commented on WICKET-6346: --- Should this be added to the dev-utils project? > Add Server-Timing