[JBoss JIRA] Created: (RF-9832) Core: new scripts initialization could occur after new request in queue
by Ilya Shaikovsky (JIRA)
Core: new scripts initialization could occur after new request in queue
-----------------------------------------------------------------------
Key: RF-9832
URL: https://jira.jboss.org/browse/RF-9832
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: core
Affects Versions: 3.3.3.Final
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
Priority: Critical
Fix For: Future_3.X
from 3.3.x ajax.js:
evalScripts : function(node, isLast){
var newscripts = this.getElementsByTagName("script",node);
LOG.debug("Scripts in updated part count : " + newscripts.length);
if( newscripts.length > 0 ){
var _this = this;
window.setTimeout(function() {
for (var i = 0; i < newscripts.length; i++){
_this._evaluateScript(newscripts[i]);
}
newscripts = null;
if (isLast)
{
_this.doFinish();
}
_this = undefined;
}, 0);
} else
{
if (isLast)
{
this.doFinish();
}
}
},
last doFinish call not wrapped to setTimeout. So if the last updateable area do not has scripts to be evaluated and another request already exist in queue - it will befired *before* all the scripts evaluated.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (RF-9672) autocomplete: table layout problems
by Ilya Shaikovsky (JIRA)
autocomplete: table layout problems
-----------------------------------
Key: RF-9672
URL: https://jira.jboss.org/browse/RF-9672
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Milestone4
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
Priority: Critical
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false" layout="table"
autocompleteList="#{capitalsBean.capitals}" var="cap" fetchValue="#{cap.name}">
<rich:column>
#{cap.name}
</rich:column>
<rich:column>
#{cap.state}
</rich:column>
</rich:autocomplete>
I'm seeing autocomplete list populated fine with values in table layout initially.
But when I start to navigate using down button there are tow problems:
1) not the whole row but single td selected
2) as a result of 1) you should press down so much times as much td's in row to get to next row.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (RF-9644) Calendar: attribute direction doesn't work
by Pavol Pitonak (JIRA)
Calendar: attribute direction doesn't work
------------------------------------------
Key: RF-9644
URL: https://jira.jboss.org/browse/RF-9644
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Milestone3
Environment: RichFaces 4.0.0-SNAPSHOT r.19919
Metamer 4.0.0-SNAPSHOT r.19925
Mojarra 2.0.2-FCS
GlassFish Server Open Source Edition 3.0.1
OpenJDK Runtime Environment 1.6.0_18-b18 @ Linux
Chrome 7.0.517.41 @ Linux x86_64
Reporter: Pavol Pitonak
When attribute direction is not defined at all, popup is shown correctly.
When attribute direction is set to top-left, top-right, bottom-left, bottom-right, auto or null, input is not visible because of popup (see screenshot).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months