[jira] [Commented] (TOBAGO-1311) Method prepareRender() will not be called for tree nodes in sheets

2013-09-16 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/TOBAGO-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768192#comment-13768192
 ] 

Hudson commented on TOBAGO-1311:


SUCCESS: Integrated in tobago-trunk #1104 (See 
[https://builds.apache.org/job/tobago-trunk/1104/])
TOBAGO-1311: Method prepareRender() will not be called for tree nodes in sheets 
 - this is turned off in the moment, because otherwise we got an 
NullPointerException
 - the problem is, that there is no rowId set
   - a solution would be, to set (lofwyr: 
http://svn.apache.org/viewvc/?view=revrev=1523549)
* 
/myfaces/tobago/trunk/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SheetRenderer.java


 Method prepareRender() will not be called for tree nodes in sheets
 --

 Key: TOBAGO-1311
 URL: https://issues.apache.org/jira/browse/TOBAGO-1311
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
Affects Versions: 2.0.0-alpha-1
Reporter: Udo Schnurpfeil
Priority: Minor

  - this is turned off in the moment, because otherwise we got an 
 NullPointerException
  - the problem is, that there is no rowId set
- a solution would be, to iterate over each row in the sheet, but this 
 might be an performance issue
- for performance we may make it configurable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (MYFACES-3683) Implement AjaxBehavior resetValues and delay

2013-09-16 Thread Dora Rajappan (JIRA)

[ 
https://issues.apache.org/jira/browse/MYFACES-3683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768294#comment-13768294
 ] 

Dora Rajappan commented on MYFACES-3683:


Please apply the UIInput.patch that is left out and then only the value is 
reset. When more than one ajax reset request is send javax.faces.partial.render 
param returns only one. For below request javax.faces.partial.render param 
returns only userNo.

h:commandButton type=check id=check  value=check 
   f:ajax event=click execute=userNo resetValues=true render=userNo/
f:ajax event=click execute=userName resetValues=true 
render=userName/
/h:commandButton

Requst header has this formData.

helloForm:userNo:2
helloForm:userName:custom presentation
helloForm_SUBMIT:1
javax.faces.ViewState:RrFAKI8lcND1R4ZMRKwzARHaTOpbn8JtnYLjjPIxee3xkJtlQ+cRADxFWrV+tRFX2E0XEh3Xo2w/GNMC49C4nMAIS0rORlUFGRsj5wWIGWDeBeQaqKd34YRvafwCX8eCoQf7yoSDkad0JbdJpZ6vb4oNaA7U9PjyH4YOQyjKMkbIUATRwBxOYXbuki6wr49famX3YZ5RffB8ajkdd/28qO/+BUNsiL8RQ8u6BA==
javax.faces.behavior.event:click
javax.faces.partial.event:click
javax.faces.source:helloForm:check
javax.faces.partial.ajax:true
javax.faces.partial.resetValues:true
javax.faces.partial.execute:helloForm:userNo
javax.faces.partial.render:helloForm:userNo
helloForm:helloForm

 Implement AjaxBehavior resetValues and delay
 

 Key: MYFACES-3683
 URL: https://issues.apache.org/jira/browse/MYFACES-3683
 Project: MyFaces Core
  Issue Type: Task
  Components: JSR-344
Reporter: Leonardo Uribe
 Attachments: MYFACES-3683-delay1.patch, MYFACES-3683-delay2.patch, 
 MYFACES-3683-delay3.patch, resetValuesNew.patch, resetValues.patch, 
 UIInput.patch


 Implement AjaxBehavior resetValues and delay as described in the spec. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (TRINIDAD-2399) support css client side rules in skinning framework

2013-09-16 Thread Scott O'Bryan (JIRA)

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott O'Bryan resolved TRINIDAD-2399.
-

   Resolution: Fixed
Fix Version/s: 2.1.0-core

 support css client side rules in skinning framework
 ---

 Key: TRINIDAD-2399
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2399
 Project: MyFaces Trinidad
  Issue Type: New Feature
  Components: Skinning
Affects Versions: 2.1.0-core
Reporter: Anand V Nath
Assignee: Scott O'Bryan
 Fix For: 2.1.0-core

 Attachments: jira-2399.patch


 This ER is for introducing client side css rule support in skinning framework.
 Here's a list of known CSS at-rules:
 @document - uses nested selectors that need to be resolved
 @font-face - probably safe to blindly pass through
 @keyframes - probably safe to blindly pass through
 @media - uses nested selectors that need to be resolved
 @page - probably safe to blindly pass through
 @supports - uses nested selectors that need to be resolved
 These rules can be split into two based on its usage:
 @document, @keyframes, @media, @support uses following syntax:
 @rule {
   selector 
   { 
 property : value; 
 property : value; 
 property : value; 
   }
 }
 @font-face and @page uses following syntax:
 @rule {
   property : value; 
   property : value; 
   property : value; 
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TOBAGO-1228) Setting JSF 2.0 as default version for Tobago

2013-09-16 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/TOBAGO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768410#comment-13768410
 ] 

Hudson commented on TOBAGO-1228:


SUCCESS: Integrated in tobago-trunk #1106 (See 
[https://builds.apache.org/job/tobago-trunk/1106/])
TOBAGO-1228: Setting JSF 2.0 as default version for Tobago
 - using UINamingContainer.getSeparatorChar(context) instead of 
NamingContainer.SEPARATOR_CHAR (lofwyr: 
http://svn.apache.org/viewvc/?view=revrev=1523696)
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesInvokeOnComponent12.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesUtilsEL.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUIPopup.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUISheet.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/util/FindComponentUtils.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/util/ComponentUtils.java
* 
/myfaces/tobago/trunk/tobago-extension/tobago-deprecation/src/main/java/org/apache/myfaces/tobago/renderkit/html/HtmlRendererUtil.java
* 
/myfaces/tobago/trunk/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SelectManyCheckboxRenderer.java
* 
/myfaces/tobago/trunk/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/SelectOneRadioRenderer.java
* 
/myfaces/tobago/trunk/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/TreeListboxNodeRenderer.java
* 
/myfaces/tobago/trunk/tobago-theme/tobago-theme-scarborough/src/main/java/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/tag/TreeSelectRenderer.java
* 
/myfaces/tobago/trunk/tobago-theme/tobago-theme-standard/src/main/java/org/apache/myfaces/tobago/renderkit/html/util/HtmlRendererUtils.java


 Setting JSF 2.0 as default version for Tobago
 -

 Key: TOBAGO-1228
 URL: https://issues.apache.org/jira/browse/TOBAGO-1228
 Project: MyFaces Tobago
  Issue Type: Task
Affects Versions: 1.6.0-beta-2
Reporter: Udo Schnurpfeil
Assignee: Udo Schnurpfeil
 Fix For: 2.0.0-alpha-1, 2.0.0


 It is to be defined, if we longer support JSF 1.2 for Tobago 1.6.x. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (TRINIDAD-2414) non namespaced selectors are getting compressed with skin compression turned on

2013-09-16 Thread Scott O'Bryan (JIRA)

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott O'Bryan reopened TRINIDAD-2414:
-

  Assignee: Scott O'Bryan

This issue was apparently not supposed to be closed yet

 non namespaced selectors are getting compressed with skin compression turned 
 on
 ---

 Key: TRINIDAD-2414
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2414
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Skinning
Affects Versions: 2.1.0-core
Reporter: Anand V Nath
Assignee: Scott O'Bryan
 Attachments: jira-2414.patch


 Selectors such as:
 .AFSelector { ... }
 was getting rendered in both compressed and uncompressed way with compression 
 turned on.
 But this was not happening for
 .AFSelector af|foo { ... }
 af|foo.AFSelector { ... }
 This was rendered as compressed with compression turned on. 
 The solution is to render the non namespaced selectors only in un compressed 
 format.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (MYFACES-3775) [perf] optional early flush

2013-09-16 Thread Gerhard Petracek (JIRA)
Gerhard Petracek created MYFACES-3775:
-

 Summary: [perf] optional early flush
 Key: MYFACES-3775
 URL: https://issues.apache.org/jira/browse/MYFACES-3775
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-344
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek


in project-stage production it should be possible to enable an early flush via 
context-param (performed at the end of HtmlHeadRenderer#encodeEnd)

(see http://developer.yahoo.com/performance/rules.html#flush)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TOBAGO-1228) Setting JSF 2.0 as default version for Tobago

2013-09-16 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/TOBAGO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768472#comment-13768472
 ] 

Hudson commented on TOBAGO-1228:


SUCCESS: Integrated in tobago-trunk #1107 (See 
[https://builds.apache.org/job/tobago-trunk/1107/])
TOBAGO-1228: Setting JSF 2.0 as default version for Tobago
  - clean up (lofwyr: http://svn.apache.org/viewvc/?view=revrev=1523714)
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/application/LabelValueBindingFacesMessage.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesUtilsEL.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/taglib/extension/SelectBooleanCheckboxExtensionTag.java
TOBAGO-1228: Setting JSF 2.0 as default version for Tobago
  - clean up (lofwyr: http://svn.apache.org/viewvc/?view=revrev=1523707)
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesInvokeOnComponent12.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesUtils.java
* 
/myfaces/tobago/trunk/tobago-extension/tobago-deprecation/src/main/java/org/apache/myfaces/tobago/compat
* 
/myfaces/tobago/trunk/tobago-extension/tobago-deprecation/src/main/java/org/apache/myfaces/tobago/compat/FacesInvokeOnComponent12.java
* 
/myfaces/tobago/trunk/tobago-extension/tobago-deprecation/src/main/java/org/apache/myfaces/tobago/compat/FacesUtils.java
TOBAGO-1228: Setting JSF 2.0 as default version for Tobago
  - updating event handling
  - using MethodExpression instead of MethodBinding (lofwyr: 
http://svn.apache.org/viewvc/?view=revrev=1523702)
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesUtils.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/compat/FacesUtilsEL.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/event/SheetStateChangeSource2.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/event/TabChangeSource2.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/facelets/SheetStateChangeSourceRule.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/facelets/SortActionSourceRule.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/facelets/TabChangeListenerHandler.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/facelets/TabChangeSourceRule.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUISheet.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/component/AbstractUITabGroup.java
* 
/myfaces/tobago/trunk/tobago-core/src/main/java/org/apache/myfaces/tobago/internal/taglib/component/TabChangeListenerTag.java
* 
/myfaces/tobago/trunk/tobago-example/tobago-example-demo/src/main/java/org/apache/myfaces/tobago/example/demo/TobagoDemoController.java
* 
/myfaces/tobago/trunk/tobago-example/tobago-example-demo/src/main/java/org/apache/myfaces/tobago/example/demo/actionlistener/SimpleTabChangeListener.java


 Setting JSF 2.0 as default version for Tobago
 -

 Key: TOBAGO-1228
 URL: https://issues.apache.org/jira/browse/TOBAGO-1228
 Project: MyFaces Tobago
  Issue Type: Task
Affects Versions: 1.6.0-beta-2
Reporter: Udo Schnurpfeil
Assignee: Udo Schnurpfeil
 Fix For: 2.0.0-alpha-1, 2.0.0


 It is to be defined, if we longer support JSF 1.2 for Tobago 1.6.x. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Resolved] (MYFACES-3775) [perf] optional early flush

2013-09-16 Thread Gerhard Petracek (JIRA)

 [ 
https://issues.apache.org/jira/browse/MYFACES-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gerhard Petracek resolved MYFACES-3775.
---

Resolution: Fixed

 [perf] optional early flush
 ---

 Key: MYFACES-3775
 URL: https://issues.apache.org/jira/browse/MYFACES-3775
 Project: MyFaces Core
  Issue Type: Improvement
  Components: JSR-344
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek
 Fix For: 2.2.0


 in project-stage production it should be possible to enable an early flush 
 via context-param (performed at the end of HtmlHeadRenderer#encodeEnd)
 (see http://developer.yahoo.com/performance/rules.html#flush)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (TRINIDAD-2415) nested selectors not generated correctly when used with icon selectors

2013-09-16 Thread Anand V Nath (JIRA)

[ 
https://issues.apache.org/jira/browse/TRINIDAD-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769187#comment-13769187
 ] 

Anand V Nath commented on TRINIDAD-2415:


r1522914 | sobryan | 2013-09-13 18:43:15 +0530 (Fri, 13 Sep 2013) | 5 lines

TRINIDAD-2415 - nested selectors not generated correctly when used with icon 
selectors

Thanks for the patch Anand

 nested selectors not generated correctly when used with icon selectors
 --

 Key: TRINIDAD-2415
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2415
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Skinning
Affects Versions: 2.1.0-core
Reporter: Anand V Nath
 Attachments: jira-2415-new.patch, jira-2415.patch


 This bug is about a nested selector specified with an -icon selector.
 Eg: .AFSomeAlias af|style-icon or .AFSomeAlias af|style-icon:hover
 This gets rendered as
 AFSomeAlias af_style-icon
 AFSomeAlias af_style-icon:hover
 The reason why this happens is that we strip out the leading dot for the icon 
 styles. But it is required only for the icon alias cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (TRINIDAD-2415) nested selectors not generated correctly when used with icon selectors

2013-09-16 Thread Anand V Nath (JIRA)

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Anand V Nath updated TRINIDAD-2415:
---

   Resolution: Fixed
Fix Version/s: 2.1.0-core
   Status: Resolved  (was: Patch Available)

r1522914 | sobryan | 2013-09-13 18:43:15 +0530 (Fri, 13 Sep 2013) | 5 lines



 nested selectors not generated correctly when used with icon selectors
 --

 Key: TRINIDAD-2415
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2415
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Skinning
Affects Versions: 2.1.0-core
Reporter: Anand V Nath
 Fix For: 2.1.0-core

 Attachments: jira-2415-new.patch, jira-2415.patch


 This bug is about a nested selector specified with an -icon selector.
 Eg: .AFSomeAlias af|style-icon or .AFSomeAlias af|style-icon:hover
 This gets rendered as
 AFSomeAlias af_style-icon
 AFSomeAlias af_style-icon:hover
 The reason why this happens is that we strip out the leading dot for the icon 
 styles. But it is required only for the icon alias cases.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (TRINIDAD-2408) TrPage._getTextContent is not working in IE10

2013-09-16 Thread Paresh Kumar Acharya (JIRA)

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paresh Kumar Acharya reopened TRINIDAD-2408:



The fix needs a minor change to solve the issue.

 TrPage._getTextContent is not working in IE10
 -

 Key: TRINIDAD-2408
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2408
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 2.0.0-core, 2.1.0-core
 Environment: IE-10
Reporter: Paresh Kumar Acharya
Assignee: Scott O'Bryan
 Fix For: 2.0.2-core, 2.1.0-core

 Attachments: 17285610.patch, IE10-Test3.zip


 The TrPage._getTextContent() API is not working on ie 10. On ie10 the 
 innerText attribute and the text attribute doesn't work on IE10. In IE 10 
 textContent attribute shoule be used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (TRINIDAD-2408) TrPage._getTextContent is not working in IE10

2013-09-16 Thread Paresh Kumar Acharya (JIRA)

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paresh Kumar Acharya updated TRINIDAD-2408:
---

Status: Patch Available  (was: Reopened)

 TrPage._getTextContent is not working in IE10
 -

 Key: TRINIDAD-2408
 URL: https://issues.apache.org/jira/browse/TRINIDAD-2408
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 2.0.0-core, 2.1.0-core
 Environment: IE-10
Reporter: Paresh Kumar Acharya
Assignee: Scott O'Bryan
 Fix For: 2.0.2-core, 2.1.0-core

 Attachments: 17285610.patch, IE10-Test3.zip


 The TrPage._getTextContent() API is not working on ie 10. On ie10 the 
 innerText attribute and the text attribute doesn't work on IE10. In IE 10 
 textContent attribute shoule be used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira