[jira] [Updated] (TAP5-2274) AjaxFormLoop doesn't work well inside a table tag

[ https://issues.apache.org/jira/browse/TAP5-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2274: - Fix Version/s: (was: 5.4) > AjaxFormLoop doesn't work well inside a table tag >

[jira] [Updated] (TAP5-2520) NullPointerException in CaseInsensitiveMap

[ https://issues.apache.org/jira/browse/TAP5-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2520: - Component/s: tapestry-ioc tapestry-core > NullPointerException in

[jira] [Updated] (TAP5-2520) NullPointerException in CaseInsensitiveMap

[ https://issues.apache.org/jira/browse/TAP5-2520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2520: - Description: {code} java.lang.NullPointerException: null at

[jira] [Created] (TAP5-2520) NullPointerException in CaseInsensitiveMap

Jochen Kemnade created TAP5-2520: Summary: NullPointerException in CaseInsensitiveMap Key: TAP5-2520 URL: https://issues.apache.org/jira/browse/TAP5-2520 Project: Tapestry 5 Issue Type:

[jira] [Updated] (TAP5-2505) Different behavior of ElementWrapper.visible with jQuery and Prototype

[ https://issues.apache.org/jira/browse/TAP5-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2505: - Component/s: tapestry-core > Different behavior of ElementWrapper.visible with jQuery and

[jira] [Commented] (TAP5-1377) Combine CSS files in production mode

[ https://issues.apache.org/jira/browse/TAP5-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035511#comment-15035511 ] Jochen Kemnade commented on TAP5-1377: -- I just had another idea: Stylesheets can be added to

[jira] [Updated] (TAP5-1772) IOC Circular dependency results in StackOverflowError

[ https://issues.apache.org/jira/browse/TAP5-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-1772: - Attachment: 0001-TAP5-1772-add-test.patch I created a test case. > IOC Circular dependency

[jira] [Updated] (TAP5-1772) IOC Circular dependency results in StackOverflowError

[ https://issues.apache.org/jira/browse/TAP5-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-1772: - Affects Version/s: 5.4 > IOC Circular dependency results in StackOverflowError >

[jira] [Commented] (TAP5-2225) Create client-side API to call a component's event handler methods

[ https://issues.apache.org/jira/browse/TAP5-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028331#comment-15028331 ] Jochen Kemnade commented on TAP5-2225: -- That sounds like a more sophisticated approach, but might be a

[jira] [Commented] (TAP5-2225) Create client-side API to call a component's event handler methods

[ https://issues.apache.org/jira/browse/TAP5-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15028641#comment-15028641 ] Jochen Kemnade commented on TAP5-2225: -- {quote} What do you mean by module? {quote} JavaScript module,

[jira] [Created] (TAP5-2515) Grid's empty parameter is not used if renderTableIfEmpty is true

Jochen Kemnade created TAP5-2515: Summary: Grid's empty parameter is not used if renderTableIfEmpty is true Key: TAP5-2515 URL: https://issues.apache.org/jira/browse/TAP5-2515 Project: Tapestry 5

[jira] [Created] (TAP5-2516) ArrayIndexOutOfBoundsException when trying to report a template parsing error

Jochen Kemnade created TAP5-2516: Summary: ArrayIndexOutOfBoundsException when trying to report a template parsing error Key: TAP5-2516 URL: https://issues.apache.org/jira/browse/TAP5-2516 Project:

[jira] [Closed] (TAP5-2517) Wrong exception reported for duplicate classpath resource

[ https://issues.apache.org/jira/browse/TAP5-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2517. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > Wrong exception

[jira] [Created] (TAP5-2517) Wrong exception reported for duplicate classpath resource

Jochen Kemnade created TAP5-2517: Summary: Wrong exception reported for duplicate classpath resource Key: TAP5-2517 URL: https://issues.apache.org/jira/browse/TAP5-2517 Project: Tapestry 5

[jira] [Updated] (TAP5-2515) Grid's empty parameter is not used if renderTableIfEmpty is true

[ https://issues.apache.org/jira/browse/TAP5-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2515: - Description: {code} {code} will render "There is no data to display." inside the td. We should

[jira] [Closed] (TAP5-2515) Grid's empty parameter is not used if renderTableIfEmpty is true

[ https://issues.apache.org/jira/browse/TAP5-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2515. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > Grid's empty

[jira] [Closed] (TAP5-2516) ArrayIndexOutOfBoundsException when trying to report a template parsing error

[ https://issues.apache.org/jira/browse/TAP5-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2516. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 >

[jira] [Commented] (TAP5-2225) Create client-side API to call a component's event handler methods

[ https://issues.apache.org/jira/browse/TAP5-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15002426#comment-15002426 ] Jochen Kemnade commented on TAP5-2225: -- [~thiagohp], do you still intend to work on this? I've started

[jira] [Commented] (TAP5-2514) Bootstrap library dependencies not loaded on Firefox

[ https://issues.apache.org/jira/browse/TAP5-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15000671#comment-15000671 ] Jochen Kemnade commented on TAP5-2514: -- I still cannot reproduce this, maybe it only happens on

[jira] [Commented] (TAP5-2514) Bootstrap library dependencies not loaded on Firefox

[ https://issues.apache.org/jira/browse/TAP5-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15000706#comment-15000706 ] Jochen Kemnade commented on TAP5-2514: -- It shouldn't have done that. Why do the old modules stick

[jira] [Commented] (TAP5-2514) Bootstrap library dependencies not loaded on Firefox

[ https://issues.apache.org/jira/browse/TAP5-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15000579#comment-15000579 ] Jochen Kemnade commented on TAP5-2514: -- I cannot reproduce this issue. Which browser are you

[jira] [Updated] (TAP5-2513) Specifying a regexp validation rule where the pattern contains a comma breaks

[ https://issues.apache.org/jira/browse/TAP5-2513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2513: - Labels: patch (was: ) > Specifying a regexp validation rule where the pattern contains a comma

[jira] [Closed] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2490. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > Autocomplete and

[jira] [Updated] (TAP5-2075) Checkbox doesn't trigger VALIDATE event

[ https://issues.apache.org/jira/browse/TAP5-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2075: - Labels: patch (was: ) > Checkbox doesn't trigger VALIDATE event >

[jira] [Closed] (TAP5-2509) Regression with radiogroup label in 5.4-beta-37

[ https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2509. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 I changed it to a

[jira] [Closed] (TAP5-2204) Select component fails if SelectModel doesn't exist on submit

[ https://issues.apache.org/jira/browse/TAP5-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2204. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > Select component

[jira] [Closed] (TAP5-1886) DateField is not localized correctly

[ https://issues.apache.org/jira/browse/TAP5-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-1886. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > DateField is not

[jira] [Commented] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991903#comment-14991903 ] Jochen Kemnade commented on TAP5-2490: -- For Select, this turns out to be much more complicated than

[jira] [Comment Edited] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991903#comment-14991903 ] Jochen Kemnade edited comment on TAP5-2490 at 11/5/15 5:09 PM: --- For Select,

[jira] [Commented] (TAP5-2509) Regression with radiogroup label in 5.4-beta-37

[ https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989520#comment-14989520 ] Jochen Kemnade commented on TAP5-2509: -- Well, TAP5-2500 did not force the change. I just assumed that

[jira] [Commented] (TAP5-2038) Many images in the Tapestry component examples are now very out of date

[ https://issues.apache.org/jira/browse/TAP5-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973929#comment-14973929 ] Jochen Kemnade commented on TAP5-2038: -- You can always run the app1 test app from the tapestry-core

[jira] [Closed] (TAP5-2482) BeanEditForm field name regression introduced with 5.4-beta-31

[ https://issues.apache.org/jira/browse/TAP5-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2482. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 I rolled back

[jira] [Updated] (TAP5-2367) Add an "alwaysSubmit" parameter to AjaxFormLoop

[ https://issues.apache.org/jira/browse/TAP5-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2367: - Labels: patch (was: ) > Add an "alwaysSubmit" parameter to AjaxFormLoop >

[jira] [Commented] (TAP5-2255) Form and BeanEditForm differ in JSR-303 detection

[ https://issues.apache.org/jira/browse/TAP5-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974377#comment-14974377 ] Jochen Kemnade commented on TAP5-2255: -- I just tried this with a simplified example and at least

[jira] [Closed] (TAP5-1237) DateField is missing finnish and swedish error messages

[ https://issues.apache.org/jira/browse/TAP5-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-1237. Resolution: Incomplete I've added the two strings but there are still a lot of missing translations:

[jira] [Comment Edited] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970658#comment-14970658 ] Jochen Kemnade edited comment on TAP5-2490 at 10/23/15 8:48 AM: I think I'm

[jira] [Commented] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970664#comment-14970664 ] Jochen Kemnade commented on TAP5-2490: -- I guess that fix would work only work in connection with a

[jira] [Updated] (TAP5-2036) Localized filenames not found if locale contains variant

[ https://issues.apache.org/jira/browse/TAP5-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2036: - Affects Version/s: 5.4 > Localized filenames not found if locale contains variant >

[jira] [Commented] (TAP5-2036) Localized filenames not found if locale contains variant

[ https://issues.apache.org/jira/browse/TAP5-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970935#comment-14970935 ] Jochen Kemnade commented on TAP5-2036: -- I'm not sure about {{foo__WIN.properties}}. Should we really

[jira] [Commented] (TAP5-2512) 5.4 breaks CSS that works unchanged in 5.3.x

[ https://issues.apache.org/jira/browse/TAP5-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970797#comment-14970797 ] Jochen Kemnade commented on TAP5-2512: -- Can you please add more information about how the CSS is

[jira] [Closed] (TAP5-2504) FormTests.datefield_leniency() fails with Prototype

[ https://issues.apache.org/jira/browse/TAP5-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2504. Resolution: Fixed Fix Version/s: 5.4 The issue is fixed, the question remains. >

[jira] [Closed] (TAP5-2397) AjaxFormLoop / DateField not operable if added by addRow event

[ https://issues.apache.org/jira/browse/TAP5-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2397. Resolution: Fixed > AjaxFormLoop / DateField not operable if added by addRow event >

[jira] [Updated] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2490: - Attachment: 0001-TAP5-2490-use-UrlEventContext-instead-of-ArrayEventC.patch I think I' able to

[jira] [Updated] (TAP5-2487) t:extension-point declaration in tapestry_*.xsd's have never been correct

[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2487: - Labels: 54_release_prerequisite (was: ) > t:extension-point declaration in tapestry_*.xsd's have

[jira] [Commented] (TAP5-2487) t:extension-point declaration in tapestry_*.xsd's have never been correct

[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14964916#comment-14964916 ] Jochen Kemnade commented on TAP5-2487: -- We should come to a decision for 5.4. > t:extension-point

[jira] [Commented] (TAP5-2511) Named AMD modules cannot be added to JavaScript stack

[ https://issues.apache.org/jira/browse/TAP5-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965132#comment-14965132 ] Jochen Kemnade commented on TAP5-2511: -- I wonder what we should do if we find a define call with a

[jira] [Commented] (TAP5-2487) t:extension-point declaration in tapestry_*.xsd's have never been correct

[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965141#comment-14965141 ] Jochen Kemnade commented on TAP5-2487: -- {{

[jira] [Commented] (TAP5-2487) t:extension-point declaration in tapestry_*.xsd's have never been correct

[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965000#comment-14965000 ] Jochen Kemnade commented on TAP5-2487: -- Yes, I think that would be the best option. >

[jira] [Closed] (TAP5-2487) t:extension-point declaration in tapestry_*.xsd's have never been correct

[ https://issues.apache.org/jira/browse/TAP5-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2487. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > t:extension-point

[jira] [Created] (TAP5-2511) Named AMD modules cannot be added to JavaScript stack

Jochen Kemnade created TAP5-2511: Summary: Named AMD modules cannot be added to JavaScript stack Key: TAP5-2511 URL: https://issues.apache.org/jira/browse/TAP5-2511 Project: Tapestry 5 Issue

[jira] [Closed] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2508. Resolution: Fixed Assignee: Jochen Kemnade Fix Version/s: 5.4 > Page activation

[jira] [Comment Edited] (TAP5-2509) Regression with radiogroup label in 5.4-beta-37

[ https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954504#comment-14954504 ] Jochen Kemnade edited comment on TAP5-2509 at 10/13/15 6:56 AM: Yes it is.

[jira] [Commented] (TAP5-2509) Regression with radiogroup label in 5.4-beta-37

[ https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14954504#comment-14954504 ] Jochen Kemnade commented on TAP5-2509: -- Yes it is. I assumed that a Label can only be used with a

[jira] [Commented] (TAP5-2509) Regression with radiogroup label in 5.4-beta-37

[ https://issues.apache.org/jira/browse/TAP5-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14953431#comment-14953431 ] Jochen Kemnade commented on TAP5-2509: -- That's probably caused by

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14950069#comment-14950069 ] Jochen Kemnade commented on TAP5-2508: -- The test suite runs fine. I'm a bit worried about

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14946495#comment-14946495 ] Jochen Kemnade commented on TAP5-2508: -- Just for the record: this issues is caused by a mix of

[jira] [Closed] (TAP5-2238) When require-ing a module that is part of a JavaScript Stack, the entire stack should be imported

[ https://issues.apache.org/jira/browse/TAP5-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2238. Resolution: Fixed > When require-ing a module that is part of a JavaScript Stack, the entire >

[jira] [Updated] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2508: - Labels: 54_release_prerequisite patch (was: patch) > Page activation method not always called

[jira] [Updated] (TAP5-2238) When require-ing a module that is part of a JavaScript Stack, the entire stack should be imported

[ https://issues.apache.org/jira/browse/TAP5-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2238: - Labels: patch (was: ) > When require-ing a module that is part of a JavaScript Stack, the entire

[jira] [Updated] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2508: - Labels: has-patch (was: ) > Page activation method not always called since t54-beta33 >

[jira] [Updated] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2508: - Labels: patch (was: has-patch) > Page activation method not always called since t54-beta33 >

[jira] [Updated] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2508: - Component/s: tapestry-core plastic > Page activation method not always called

[jira] [Updated] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2508: - Attachment: 0001-TAP5-2508-methods-with-default-visibility-cannot-be-.patch The patch should fix

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14941021#comment-14941021 ] Jochen Kemnade commented on TAP5-2508: -- Yes, me too. I've traced it down to {{OnEventWorker:406}},

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940875#comment-14940875 ] Jochen Kemnade commented on TAP5-2508: -- Alright, got it. It's really

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939581#comment-14939581 ] Jochen Kemnade commented on TAP5-2508: -- I don't think it has something to do with dependency handling.

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939518#comment-14939518 ] Jochen Kemnade commented on TAP5-2508: -- I'm trying to debug this. [~chrispoulsen], are both methods

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939542#comment-14939542 ] Jochen Kemnade commented on TAP5-2508: -- Yes, I saw the same behavior when I tried this yesterday. But

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939565#comment-14939565 ] Jochen Kemnade commented on TAP5-2508: -- Same behavior if I import the module in Eclipse and run it

[jira] [Comment Edited] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939518#comment-14939518 ] Jochen Kemnade edited comment on TAP5-2508 at 10/1/15 8:50 AM: --- I'm trying to

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939557#comment-14939557 ] Jochen Kemnade commented on TAP5-2508: -- Funny. If I run your project with Gradle, only the method from

[jira] [Comment Edited] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14939565#comment-14939565 ] Jochen Kemnade edited comment on TAP5-2508 at 10/1/15 9:26 AM: --- Same behavior

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936735#comment-14936735 ] Jochen Kemnade commented on TAP5-2508: -- Apparently this changed between betas 28 and 29. I had a quick

[jira] [Commented] (TAP5-2508) Page activation method not always called since t54-beta33

[ https://issues.apache.org/jira/browse/TAP5-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14936781#comment-14936781 ] Jochen Kemnade commented on TAP5-2508: -- Yes, that commit message seemed slightly suspicious to me too.

[jira] [Commented] (TAP5-2489) Palette component parameter availableLabel and selectedLabel should have required = false

[ https://issues.apache.org/jira/browse/TAP5-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805090#comment-14805090 ] Jochen Kemnade commented on TAP5-2489: -- I guess that's a bug in IntelliJ or some plugin that tries to

[jira] [Closed] (TAP5-2194) Declare SubmitNotifier event names as constants to avoid typos

[ https://issues.apache.org/jira/browse/TAP5-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2194. Resolution: Fixed Fix Version/s: 5.4 The new constants are

[jira] [Updated] (TAP5-2238) When require-ing a module that is part of a JavaScript Stack, the entire stack should be imported

[ https://issues.apache.org/jira/browse/TAP5-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2238: - Attachment: 0001-TAP5-2238-if-a-module-is-requested-that-is-part-of-a.patch This patch fixes the

[jira] [Commented] (TAP5-2489) Palette component parameter availableLabel and selectedLabel should have required = false

[ https://issues.apache.org/jira/browse/TAP5-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805109#comment-14805109 ] Jochen Kemnade commented on TAP5-2489: -- No, I don't. The JavaDoc of {{Parameter.value()}} says: "The

[jira] [Commented] (TAP5-2454) Checklist and Palette should support a default encoder like Select

[ https://issues.apache.org/jira/browse/TAP5-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805335#comment-14805335 ] Jochen Kemnade commented on TAP5-2454: -- This could be done using

[jira] [Commented] (TAP5-2350) JavaScript library with module shim config is loaded twice if module is added to a stack

[ https://issues.apache.org/jira/browse/TAP5-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14805268#comment-14805268 ] Jochen Kemnade commented on TAP5-2350: -- We might be able to solve this with a similar approach to what

[jira] [Closed] (TAP5-2463) ResponseWrapper dont work correctly in dom,js

[ https://issues.apache.org/jira/browse/TAP5-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2463. Resolution: Fixed Fixed in {{a260fa25e76cf408bcf5645a8d43e171f3a27d77}} (5.4-beta-36). >

[jira] [Closed] (TAP5-2506) Report conflicting BeanBlockOverrideSource configuration

[ https://issues.apache.org/jira/browse/TAP5-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2506. Resolution: Fixed Fix Version/s: 5.4 > Report conflicting BeanBlockOverrideSource

[jira] [Created] (TAP5-2506) Report conflicting BeanBlockOverrideSource configuration

Jochen Kemnade created TAP5-2506: Summary: Report conflicting BeanBlockOverrideSource configuration Key: TAP5-2506 URL: https://issues.apache.org/jira/browse/TAP5-2506 Project: Tapestry 5

[jira] [Commented] (TAP5-2490) Autocomplete and Select context values does not work when context has to pass through a value encoder

[ https://issues.apache.org/jira/browse/TAP5-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802677#comment-14802677 ] Jochen Kemnade commented on TAP5-2490: -- [~zenios], could you please create a simple page that

[jira] [Updated] (TAP5-2506) Report conflicting BeanBlockOverrideSource configuration

[ https://issues.apache.org/jira/browse/TAP5-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2506: - Issue Type: Improvement (was: Bug) > Report conflicting BeanBlockOverrideSource configuration >

[jira] [Commented] (TAP5-2492) No change event when datePicker updates t:datefield

[ https://issues.apache.org/jira/browse/TAP5-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802904#comment-14802904 ] Jochen Kemnade commented on TAP5-2492: -- This was already requested: TAP5-2145 > No change event when

[jira] [Closed] (TAP5-2492) No change event when datePicker updates t:datefield

[ https://issues.apache.org/jira/browse/TAP5-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2492. Resolution: Duplicate > No change event when datePicker updates t:datefield >

[jira] [Created] (TAP5-2503) Confirm Mixin does not with with Prototype

Jochen Kemnade created TAP5-2503: Summary: Confirm Mixin does not with with Prototype Key: TAP5-2503 URL: https://issues.apache.org/jira/browse/TAP5-2503 Project: Tapestry 5 Issue Type: Bug

[jira] [Updated] (TAP5-2503) Confirm Mixin does not work with Prototype

[ https://issues.apache.org/jira/browse/TAP5-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2503: - Summary: Confirm Mixin does not work with Prototype (was: Confirm Mixin does not with with

[jira] [Updated] (TAP5-2503) Confirm Mixin does not work with Prototype

[ https://issues.apache.org/jira/browse/TAP5-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade updated TAP5-2503: - Description: The Confirm Mixin does not work if the JavaScript infrastructure provider is set to

[jira] [Created] (TAP5-2504) FormTests.datefield_leniency() fails with Prototype

Jochen Kemnade created TAP5-2504: Summary: FormTests.datefield_leniency() fails with Prototype Key: TAP5-2504 URL: https://issues.apache.org/jira/browse/TAP5-2504 Project: Tapestry 5 Issue

[jira] [Created] (TAP5-2505) Different behavior of ElementWrapper.visible with jQuery and Prototype

Jochen Kemnade created TAP5-2505: Summary: Different behavior of ElementWrapper.visible with jQuery and Prototype Key: TAP5-2505 URL: https://issues.apache.org/jira/browse/TAP5-2505 Project: Tapestry

[jira] [Commented] (TAP5-2505) Different behavior of ElementWrapper.visible with jQuery and Prototype

[ https://issues.apache.org/jira/browse/TAP5-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768961#comment-14768961 ] Jochen Kemnade commented on TAP5-2505: -- I wonder if we need that method anyway. We're only using it in

[jira] [Commented] (TAP5-2504) FormTests.datefield_leniency() fails with Prototype

[ https://issues.apache.org/jira/browse/TAP5-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768906#comment-14768906 ] Jochen Kemnade commented on TAP5-2504: -- The test was added for TAP5-1998. There's no client-side

[jira] [Commented] (TAP5-2504) FormTests.datefield_leniency() fails with Prototype

[ https://issues.apache.org/jira/browse/TAP5-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14768963#comment-14768963 ] Jochen Kemnade commented on TAP5-2504: -- I've changed {{deepVisible()}} to use vanilla JS, now the test

[jira] [Closed] (TAP5-2502) Tapestry5: jQuery.dialog not work with DataTables

[ https://issues.apache.org/jira/browse/TAP5-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2502. Resolution: Invalid > Tapestry5: jQuery.dialog not work with DataTables >

[jira] [Commented] (TAP5-2502) Tapestry5: jQuery.dialog not work with DataTables

[ https://issues.apache.org/jira/browse/TAP5-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14745223#comment-14745223 ] Jochen Kemnade commented on TAP5-2502: -- The DataTable and Dialog components belong to the

[jira] [Closed] (TAP5-2501) AjaxFormLoop doesn't work well inside a table tag

[ https://issues.apache.org/jira/browse/TAP5-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade closed TAP5-2501. Resolution: Duplicate > AjaxFormLoop doesn't work well inside a table tag >

[jira] [Reopened] (TAP5-2274) AjaxFormLoop doesn't work well inside a table tag

[ https://issues.apache.org/jira/browse/TAP5-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Kemnade reopened TAP5-2274: -- According to [~homburgs], the issue still exists. > AjaxFormLoop doesn't work well inside a table

[jira] [Commented] (TAP5-2500) Label broken when inside zone and attached to a Field after that zone

[ https://issues.apache.org/jira/browse/TAP5-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14738380#comment-14738380 ] Jochen Kemnade commented on TAP5-2500: -- If we only have a single Heartbeat, we need another way to

<    1   2   3   4   5   6   7   8   9   10   >