[JBoss JIRA] (RF-13311) Make Push independent of BaseComponent
by Michal Petrov (JIRA)
Michal Petrov created RF-13311:
----------------------------------
Summary: Make Push independent of BaseComponent
Key: RF-13311
URL: https://issues.jboss.org/browse/RF-13311
Project: RichFaces
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Affects Versions: 5-Tracking
Reporter: Michal Petrov
Currently Push extends BaseComponent but since BaseComponent is not a part of core the extending fails.
--
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
10 years, 5 months
[JBoss JIRA] (RF-13310) Upgrade Graphene and Warp in 4.3 branch
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13310?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13310:
----------------------------
Summary: Upgrade Graphene and Warp in 4.3 branch (was: Upgrade Graphene and Warp in 4.3.5 branch)
> Upgrade Graphene and Warp in 4.3 branch
> ---------------------------------------
>
> Key: RF-13310
> URL: https://issues.jboss.org/browse/RF-13310
> Project: RichFaces
> Issue Type: Component Upgrade
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Affects Versions: 4.3.5
> Reporter: Lukáš Fryč
>
> The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue.
> Why we want to upgrade:
> * Graphene = Final version API changes changes
> * Warp = ease of debugging
> I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik.
--
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
10 years, 5 months
[JBoss JIRA] (RF-13310) Upgrade Graphene and Warp in 4.3.5 branch
by Lukáš Fryč (JIRA)
Lukáš Fryč created RF-13310:
-------------------------------
Summary: Upgrade Graphene and Warp in 4.3.5 branch
Key: RF-13310
URL: https://issues.jboss.org/browse/RF-13310
Project: RichFaces
Issue Type: Component Upgrade
Security Level: Public (Everyone can see)
Components: tests - functional
Affects Versions: 4.3.5
Reporter: Lukáš Fryč
The state of 4.3 branch framework tests is not as stable as 5.0, thus I track this as a separate issue.
Why we want to upgrade:
* Graphene = Final version API changes changes
* Warp = ease of debugging
I don't think this is absolutely necessary, I doesn;'t work with 4.3.x tests regularly and QE doesn't run them afaik.
--
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
10 years, 5 months
[JBoss JIRA] (RF-13308) Autocomplete: clientFilterFunction doesn't work in Firefox
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-13308:
----------------------------------
Summary: Autocomplete: clientFilterFunction doesn't work in Firefox
Key: RF-13308
URL: https://issues.jboss.org/browse/RF-13308
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input, regression
Affects Versions: 5.0.0.Alpha2
Environment: RichFaces 5.0.0-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Mojarra 2.1.19
EAP 6.1.1
Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
Firefox 24 @ Linux x86_64
Reporter: Pavol Pitonak
Priority: Critical
# deploy Metamer and open http://localhost:8080/metamer/faces/components/richAutocomplete/filtering...
# set attribute mode to "client"
# set attribute clientFilterFunction to "customClientFilterFunction"
# type "no" to the autocomplete
# select "Raleigh of North Carolina"
# click outside of autocomplete in order to send selected value to the server
# check that output contains "North Carolina"
result:
* works fine in Chrome 30
* in Firefox 24, after you type "no", popup with suggestions is not displayed
* works fine in RichFaces 4.3.4.Final
--
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
10 years, 5 months
[JBoss JIRA] (RF-13307) Support java.util.Set in iteration components
by Matti Bickel (JIRA)
[ https://issues.jboss.org/browse/RF-13307?page=com.atlassian.jira.plugin.s... ]
Matti Bickel updated RF-13307:
------------------------------
Description:
JSF-2.2 now supports iteration over sets as in
{code:xml}
<h:dataTable value="#{myBean.mySet}" var="elem">
<h:column>#{elem.name}</h:column>
</h:dataTable>
{code}
Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
Would be nice if RF catches up with JSF here.
was:
JSF-2.2 now supports iteration over sets as in
<h:dataTable value="#{myBean.mySet}" var="elem">
<h:column>#{elem.name}"</h:column>
</h:dataTable>
Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
Would be nice if RF catches up with JSF here.
> Support java.util.Set in iteration components
> ---------------------------------------------
>
> Key: RF-13307
> URL: https://issues.jboss.org/browse/RF-13307
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.5-Tracking, 5.0.0.Alpha3
> Environment: Wildfly-8.0.0.Beta1
> Reporter: Matti Bickel
>
> JSF-2.2 now supports iteration over sets as in
> {code:xml}
> <h:dataTable value="#{myBean.mySet}" var="elem">
> <h:column>#{elem.name}</h:column>
> </h:dataTable>
> {code}
> Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
> Would be nice if RF catches up with JSF here.
--
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
10 years, 5 months
[JBoss JIRA] (RF-13307) Support java.util.Set in iteration components
by Matti Bickel (JIRA)
Matti Bickel created RF-13307:
---------------------------------
Summary: Support java.util.Set in iteration components
Key: RF-13307
URL: https://issues.jboss.org/browse/RF-13307
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.5-Tracking, 5.0.0.Alpha3
Environment: Wildfly-8.0.0.Beta1
Reporter: Matti Bickel
JSF-2.2 now supports iteration over sets as in
<h:dataTable value="#{myBean.mySet}" var="elem">
<h:column>#{elem.name}"</h:column>
</h:dataTable>
Using RF iteration components this is currently not possible as UISequence.java doesn't detect Sets and treats them as scalar values.
Would be nice if RF catches up with JSF here.
--
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
10 years, 5 months
[JBoss JIRA] (RF-13306) Autocomplete: ignored API call .setValue('')
by alexey plotnikov (JIRA)
alexey plotnikov created RF-13306:
-------------------------------------
Summary: Autocomplete: ignored API call .setValue('')
Key: RF-13306
URL: https://issues.jboss.org/browse/RF-13306
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.3.4
Reporter: alexey plotnikov
All described here https://community.jboss.org/thread/233973
I have this autocomplete component:
{code}
<table>
<tr>
<td>
<rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"
minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"
autofill="false"
onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"
layout="table" value="#{autocomplete.providerName}" >
<a4j:queue requestDelay="500" ignoreDupResponses="true" />
<h:column>
<h:outputText style="display:none;" value="#{s.id}"/>
<h:outputText style="display:none;" value="#{s.realName}"/>
</h:column>
<h:column>
<h:outputText value="#{s.name}" escape="false"/>
</h:column>
</rich:autocomplete>
</td>
<td>
<h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"
alt=""/>
<h:graphicImage value="/img/cancel.png"
onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"
alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>
<h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>
</td>
</tr>
</table>
{code}
as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
I use JavaScript function "autocompleteChangeProvider" for extract selected id.
I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
And a problem:
if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on show button(/img/arrow.png) than input text not erasing, but i called #{rich:component('provider-suggestion')}.setValue('') !!!
I think i found a solution
AutocompleteBase.js has this code:
{code}
rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {
// call constructor of parent class
$super.constructor.call(this, componentId);
this.selectId = selectId;
this.fieldId = fieldId;
this.options = $.extend({}, defaultOptions, options);
this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);
this.currentValue = "";
this.tempValue = this.getValue();
this.isChanged = this.tempValue.length != 0;
bindEventHandlers.call(this);
};
{code}
as you can see this.currentValue = "" so JS thinks that this.currentValue="" so currentValue equal new value("" - empty string), so nothing happens.
i replace this code by this:
{code}
rf.ui.AutocompleteBase = function(componentId, selectId, fieldId, options) {
// call constructor of parent class
$super.constructor.call(this, componentId);
this.selectId = selectId;
this.fieldId = fieldId;
this.options = $.extend({}, defaultOptions, options);
this.namespace = this.namespace || "." + rf.Event.createNamespace(this.name, this.selectId);
this.currentValue = $(rf.getDomElement(fieldId)).val();
this.tempValue = this.getValue();
this.isChanged = this.tempValue.length != 0;
bindEventHandlers.call(this);
};
{code}
and it works!
--
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
10 years, 5 months
[JBoss JIRA] (RF-13305) Autocomplete: i must press button twice for popup window
by alexey plotnikov (JIRA)
alexey plotnikov created RF-13305:
-------------------------------------
Summary: Autocomplete: i must press button twice for popup window
Key: RF-13305
URL: https://issues.jboss.org/browse/RF-13305
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.3.4
Reporter: alexey plotnikov
All described here https://community.jboss.org/thread/233971
I try repeat:
I have this autocomplete component:
{code}
<table>
<tr>
<td>
<rich:autocomplete mode="ajax" autocompleteMethod="#{autocomplete.autocompleteProviders}"
minChars="0" var="s" fetchValue="#{s.realName}" id="provider-suggestion"
autofill="false"
onselectitem="autocompleteChangeProvider(event.target)" style="display: inline;"
layout="table" value="#{autocomplete.providerName}" >
<a4j:queue requestDelay="500" ignoreDupResponses="true" />
<h:column>
<h:outputText style="display:none;" value="#{s.id}"/>
<h:outputText style="display:none;" value="#{s.realName}"/>
</h:column>
<h:column>
<h:outputText value="#{s.name}" escape="false"/>
</h:column>
</rich:autocomplete>
</td>
<td>
<h:graphicImage value="/img/arrow.png" onclick="#{rich:component('provider-suggestion')}.setValue('');#{rich:component('provider-suggestion')}.showPopup();stopEvent(event);"
alt=""/>
<h:graphicImage value="/img/cancel.png"
onclick="#{rich:component('provider-suggestion')}.hidePopup();#{rich:component('provider-suggestion')}.setValue('');autocompleteChangeProvider(null);"
alt="#{messages['pages.clear']}" title="#{messages['pages.clear']}"/>
<h:inputHidden id="filter-provider-id" value="#{autocomplete.providerId}"/>
</td>
</tr>
</table>
{code}
as you can see, i don't use showButton="true", because i need another functionality, i need erase input text before show popup window.
I use JavaScript function "autocompleteChangeProvider" for extract selected id.
I use separate button(/img/cancel.png) for erase input text, as you can see this function just use Richfaces API.
And problem:
if autocomplete.providerName not null and not empty(in rich:autocomplete) and user clicks on cancel button(img/cancel.png), then after that, if user clicks on show button(/img/arrow.png) popup not showing, user must clicks twice on this button.
*This problem shows if i use showButton from rich:autocomplete instead my show button.*
I think i found a solution of this problem:
Autocomplete.js has this code:
{code}
var onChangeValue = function (event, value, callback) {
selectItem.call(this, event);
// value is undefined if called from AutocompleteBase onChange
var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;
var oldValue = this.value;
this.value = subValue;
if ((this.options.isCachedAjax || !this.options.ajaxMode) &&
this.cache && this.cache.isCached(subValue)) {
...
} else {
if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {
this.__setInputValue(subValue);
}
if (subValue.length >= this.options.minChars) {
if ((this.options.ajaxMode || this.options.lazyClientMode) && oldValue != subValue) {
callAjax.call(this, event, callback);
}
} else {
if (this.options.ajaxMode) {
clearItems.call(this);
this.__hide(event);
}
}
}
};
{code}
for show popup this must be true:
{code}
oldValue != subValue
{code}
but in this part of code
oldValue is ''(empty string) and subValue is ''(empty string),
so this condition
{code}
oldValue != subValue
{code}
return false!
i replace this code by this:
{code}
var onChangeValue = function (event, value, callback) {
selectItem.call(this, event);
// value is undefined if called from AutocompleteBase onChange
var subValue = (typeof value == "undefined") ? this.__getSubValue() : value;
var oldValue = this.value;
this.value = subValue;
if ((this.options.isCachedAjax || !this.options.ajaxMode) &&
this.cache && this.cache.isCached(subValue)) {
...
} else {
if (event.keyCode == rf.KEYS.RETURN || event.type == "click") {
this.__setInputValue(subValue);
}
if (subValue.length >= this.options.minChars) {
if ((this.options.ajaxMode || this.options.lazyClientMode) && (oldValue != subValue || (oldValue === '' && subValue === ''))) {
callAjax.call(this, event, callback);
}
} else {
if (this.options.ajaxMode) {
clearItems.call(this);
this.__hide(event);
}
}
}
};
{code}
so, than oldValue='' and subValue=='' callAjax.call will be called and popup will be showing.
--
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
10 years, 5 months