[JBoss JIRA] Created: (RF-10853) dataScroller: do not works with a4j:status properly
by Ilya Shaikovsky (JIRA)
dataScroller: do not works with a4j:status properly
---------------------------------------------------
Key: RF-10853
URL: https://issues.jboss.org/browse/RF-10853
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
1) do not works properly with form scoped default status. onstart called but onstop - not.
Problem seems in dataScroller because the same case with the button works see [1]
2) do not works at all using status="status". Seems just not implemented.
[1]
<rich:popupPanel id="splash" autosized="true" width="200" height="80" moveable="false" resizeable="false">
<f:facet name="header"><h:outputText value="WAIT" /></f:facet>
<h:outputText value="WAIT!" />
</rich:popupPanel>
<h:form id="form">
<a4j:status onstart="#{rich:component('splash')}.show()" onstop="#{rich:component('splash')}.hide()" />
<h:panelGrid columnClasses="acent">
<rich:dataScroller for="table" maxPages="5" />
<rich:dataTable value="#{carsBean.allInventoryItems}" var="car"
id="table" rows="#{userBean.age}">
................
</rich:dataTable>
<rich:dataScroller for="table" maxPages="5" status="status"/>
</h:panelGrid>
<a4j:commandButton ></a4j:commandButton>
</h:form>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (RF-10866) Queue: RF queuing rules applied to any ajax including standard f: one
by Ilya Shaikovsky (JIRA)
Queue: RF queuing rules applied to any ajax including standard f: one
---------------------------------------------------------------------
Key: RF-10866
URL: https://issues.jboss.org/browse/RF-10866
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
<a4j:queue requestDelay="1000"></a4j:queue>
<h:form>
<h:inputText value="#{userBean.name}">
<f:ajax event="keyup" render="out" />
</h:inputText>
<h:outputText value="#{userBean.name}" id="out" />
</h:form>
<a4j:log/>
while typing you could see that delay applied and requests combined.
could influence standard/third-party components. So need to review and probably remove. (at least make switchable)
setting tran label just to review early and not for impl.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (RF-10862) Autocomplete: does not perform decode of the behaviors
by Ilya Shaikovsky (JIRA)
Autocomplete: does not perform decode of the behaviors
------------------------------------------------------
Key: RF-10862
URL: https://issues.jboss.org/browse/RF-10862
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
http://community.jboss.org/message/598526#598526
checked with
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false"
autocompleteMethod="#{autocompleteBean.autocomplete}" valueChangeListener="#{autocompleteBean.vcl}">
<a4j:ajax listener="#{autocompleteBean.list}" event="change"/>
</rich:autocomplete>
<h:inputText>
<a4j:ajax listener="#{autocompleteBean.list}" event="change"/>
</h:inputText>
input calls listener and autocomplete not. Text renderer performs String clientId = decodeBehaviors(context, component);
and in autocomplete there is no such code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] Created: (RF-10892) components listed in the description were quite difficult to hit
by Juraj Huska (JIRA)
components listed in the description were quite difficult to hit
----------------------------------------------------------------
Key: RF-10892
URL: https://issues.jboss.org/browse/RF-10892
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: mobile
Affects Versions: 4.0.0.Final
Reporter: Juraj Huska
Priority: Minor
1.The numbers of pages on dataScroller, mainly when there is lot of other clickable components - iPhone
2.The plus sign in the trees, mainly not the first level plus sign, but some sublevels plus signs - Nexus
3.The cross, which should cancel the poppup modal panel. iPhone, iPad
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months