[JBoss JIRA] (RF-12862) Evaluate how hard it would be to migrate jsf-test for components (using HtmlUnitEnvironment) to fundamental tests
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12862?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12862:
---------------------------------
It is conceptually very close to other Arquillian embedded containers, so it shouldn't be hard.
> Evaluate how hard it would be to migrate jsf-test for components (using HtmlUnitEnvironment) to fundamental tests
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-12862
> URL: https://issues.jboss.org/browse/RF-12862
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha1
>
>
> The advantage of migrating the tests is improved debuggability.
> It seems that migration of the component-specific tests is pretty straight-forward, the proof of concept was done for [{{AjaxValidationTest}}|https://github.com/richfaces/richfaces5/commit/bf0f460dada7530cfc43de7837ce98c073bbb5af#diff-8].
> We need to evaluate how much of similar tests we have and if it's worth to migrate them.
--
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
11 years, 9 months
[JBoss JIRA] (RF-12862) Evaluate how hard it would be to migrate jsf-test for components (using HtmlUnitEnvironment) to fundamental tests
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12862?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12862:
------------------------------------
How hard would it be to port the jsf-test mock container to work with Arquillian?
> Evaluate how hard it would be to migrate jsf-test for components (using HtmlUnitEnvironment) to fundamental tests
> -----------------------------------------------------------------------------------------------------------------
>
> Key: RF-12862
> URL: https://issues.jboss.org/browse/RF-12862
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: tests - functional
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha1
>
>
> The advantage of migrating the tests is improved debuggability.
> It seems that migration of the component-specific tests is pretty straight-forward, the proof of concept was done for [{{AjaxValidationTest}}|https://github.com/richfaces/richfaces5/commit/bf0f460dada7530cfc43de7837ce98c073bbb5af#diff-8].
> We need to evaluate how much of similar tests we have and if it's worth to migrate them.
--
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
11 years, 9 months
[JBoss JIRA] (RF-12860) AccordionItem.js with error cause browser crash
by Jan Papousek (JIRA)
[ https://issues.jboss.org/browse/RF-12860?page=com.atlassian.jira.plugin.s... ]
Jan Papousek commented on RF-12860:
-----------------------------------
I've added some code you've mentioned to my sample.
{code}
<h:form>
<rich:extendedDataTable
value="#{testBean.people}" var="person" style="width:500px"
rows="10" sortMode="multi" selectionMode="multiple"
tableState="#{testBean.state}" noDataLabel="No Data"
onselectionchange="alert('selection change');">
<f:facet name="header">
<h:outputText value="People"/>
</f:facet>
<rich:column sortBy="#{person.firstname}" width="250px">
<f:facet name="header">First Name</f:facet>
#{person.firstname}
</rich:column>
<rich:column sortBy="#{person.secondname}" width="250px">
<f:facet name="header">Second Name</f:facet>
#{person.secondname}
</rich:column>
<a4j:ajax event="selectionchange" listener="#{testBean.selectionListener}" />
</rich:extendedDataTable>
<rich:accordion switchType="ajax" width="500px" style="margin-top: 50px">
<rich:accordionItem header="First item">...</rich:accordionItem>
<rich:accordionItem header="Second item">...</rich:accordionItem>
<rich:accordionItem header="Second item">...</rich:accordionItem>
</rich:accordion>
</h:form>
{code}
Still I am not able to reproduce the issue. Could you provide one of these?
# my sample application available on https://github.com/papousek/richfaces-sanbox/tree/RF-12860 updated to reproduce the issue, or
# minimal xhtml page + backing bean reproducing issue
> AccordionItem.js with error cause browser crash
> -----------------------------------------------
>
> Key: RF-12860
> URL: https://issues.jboss.org/browse/RF-12860
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.Final
> Environment: JBOSS7/JSF2/FirefoxESR10 or Chrome25.0.1
> Reporter: David Lee
> Assignee: Jan Papousek
> Labels: javascript, rich:accordionItem
> Fix For: 4.3.2
>
>
> Put the rich:accordionItem and rich:extendedDataTable on same page,
> and just click on any column for sort.
> The firebug will show an error:
> items[i].__header is not a function
> [Break On This Error]
> h -= items[i].__header().outerHeight();
> Looks like accordionItem.js line48 been triggered when sort:
> $(document).one("javascriptServiceComplete", function () {
> item.__fitToHeight(item.getTogglePanel());
> });
> And after this happened, my whole thing crashed.
> Now more sortable or click for any action.
--
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
11 years, 9 months