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

2013-07-04 Thread Anand V Nath (JIRA)
Anand V Nath created TRINIDAD-2399:
--

 Summary: 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


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] (MYFACES-3683) Implement AjaxBehavior resetValues and delay

2013-07-04 Thread Dora Rajappan (JIRA)

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

Dora Rajappan commented on MYFACES-3683:


In this scenario updatemodelvalue is called after process partial. Problem is 
in UIInput resetValue method sets LocalValueSet to false and the update model 
ignores the change. So I change UIInput resetValue method to set LocalValueSet 
to true.

> 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
>
>
> 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] [Commented] (TOMAHAWK-1664) t:selectBooleanCheckbox / Binding is not working after Mojarra update

2013-07-04 Thread Michael D. (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699814#comment-13699814
 ] 

Michael D. commented on TOMAHAWK-1664:
--

I noticed also, that now also some tags t:selectBooleanCheckbox rendered twice 
and some get the some ID, so the JSF renderer fails.

> t:selectBooleanCheckbox / Binding is not working after Mojarra update
> -
>
> Key: TOMAHAWK-1664
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1664
> Project: MyFaces Tomahawk
>  Issue Type: Bug
>Affects Versions: 1.1.13, 1.1.14
> Environment: GlassFish Server Open Source Edition 3.1.2.2 (build 5)
> - Windows 7 (64 Bit) & Oracle Java jdk1.7.0_15 (64 Bit)
> - Oracle Linux Server release 5.5 & OpenJDK 64-Bit Server VM (build 
> 1.6.0-b09, mixed mode)
> - Mojarra v2.1.23
> - org.apache.myfaces.tomahawk:tomahawk20:1.1.13
> - org.apache.myfaces.tomahawk:tomahawk20:1.1.14
> - org.apache.myfaces.tomahawk:tomahawk21:1.1.14
>Reporter: Michael D.
>
> After updating Mojarra from v2.1.6 to v2.1.23 I'm facing the issue, that the 
> binding of t:selectBooleanCheckbox is not working.
> JSF snippet:
> --- SNIP ---
>  id="myId"
> forceId="true"
> value="#{myBean.myValue}"
> binding="#{myBean.myBinding}"
> styleClass="myClass"/>
>  id="anotherId"
> value="#{myBean.anotherValue}"
> validator="#{myBean.validate}"
> requiredMessage="#{msg['required']}"
> maxlength="100"/>
> --- SNAP 
> Java snippet:
> --- SNIP ---
> @ManagedBean
> public class MyBean {
> private UIInput myBinding;
> private boolean myValue;
> private String anotherValue;
> // ...
> public UIInput getMyBinding() { return myBinding; }
> public void setMyBinding(UIInput myBinding) { this.myBinding = myBinding; 
> }
> public boolean isMyValue() { return myValue; }
> public void setMyValue(boolean myValue) { this.myValue = myValue; }
> public String getAnotherValue() { return anotherValue; }
> public void setAnotherValue(String anotherValue) { this.anotherValue = 
> anotherValue; }
> public void validate(FacesContext ctx, UIComponent comp, Object value) 
> throws ValidatorException {
> if ((HtmlSelectBooleanCheckbox) myBinding.isSelected()) { // 
> <--- myBinding is null
> // ...
> }
> }
> }
> --- SNAP ---
> 
> I did debug:
> 1. Opening page
> a) getMyBinding is called
> b) setMyBinding is called with valid instance
> 2. Submit form
> a) No call of getMyBinding/setMyBinding
> b) validate is called ---> myBinding is null
> If I replace "t:selectBooleanCheckbox" by "h:selectBooleanCheckbox":
> 1. Opening page
> a) getMyBinding is called
> b) setMyBinding is called with valid instance
> 2. Submit form
> a) setMyBinding is called with valid instance
> b) validate is called ---> myBinding is valid
> 3. Next page is displayed

--
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