[JBoss JIRA] Created: (RF-5396) Editor: "tabindex" attribute does not work.
by Alexander Dubovsky (JIRA)
Editor: "tabindex" attribute does not work.
-------------------------------------------
Key: RF-5396
URL: https://jira.jboss.org/jira/browse/RF-5396
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.0
Environment: 3.3.0.BETA4
Reporter: Alexander Dubovsky
Assignee: Nick Belaevski
"tabindex" attribute does not work in Editor.
Description for attribute:
"Tabindex" enables you to specify an element ID to focus, when the user pressed the tab key inside the
editor. You can also use the special ":prev" and ":next" values. It will then places the focus on either
the previous or next input element placed before/after the TinyMCE instance in the DOM.
Nothing from listed above does not work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-7271) IE problem when deploying richfaces portlet with WebLogic Portal
by Andreanes Yosef Vanderlee (JIRA)
IE problem when deploying richfaces portlet with WebLogic Portal
----------------------------------------------------------------
Key: RF-7271
URL: https://jira.jboss.org/jira/browse/RF-7271
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.3.1
Environment: Oracle Workshop for Weblogic 10.3 + Oracle WebLogic Portal 10.3
Reporter: Andreanes Yosef Vanderlee
If we open richfaces portlet which deployed under WLP 10.3 with Internet Explorer (6.0.2900.5512), the page won't display correctly.
Step to reproduce:
1. Create a weblogic portal project with oracle workspace
2. Create any richfaces page and make its portlet using jboss portlet bridge
3. Create New portlet which point to #2
4. set async content in portlet #3 to ajax => this is what raise the error
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-7372) rich page: facets 'header', 'footer' and 'sidebar' facets locations depend on locations in a page.
by Mikhail Vitenkov (JIRA)
rich page: facets 'header', 'footer' and 'sidebar' facets locations depend on locations in a page.
--------------------------------------------------------------------------------------------------
Key: RF-7372
URL: https://jira.jboss.org/jira/browse/RF-7372
Project: RichFaces
Issue Type: Bug
Components: component-output
Affects Versions: 3.3.2.CR1
Environment: IE6, IE7, IE8, FF2, FF3.0.10, Safari 3.1, Opera 9.62, Chrome 1.0.154.43(3.3.2.CR1)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Priority: Minor
#1. Add rich:page component with all supported facets on a page following way:
<rich:page sidebarPosition="left">
<f:facet name="sidebar">
<div>Sidebar content goes here</div>
</f:facet>
<f:facet name="footer">
<div>Footer content goes here</div>
</f:facet>
<f:facet name="header">
<div>Header content goes here</div>
</f:facet>
</rich:page>
#2. Navigate to the page and verify facets order.
Actual behavior:
Sidebar is the first, then footer, then header.
Expected behavior:
Facets order shouldn't depends on facets page location. For exampe, add following code on a page and verify facets order:
<h:form id="formID">
<h:dataTable value="" var="row">
<f:facet name="footer">
<h:outputText value="FOOTER" />
</f:facet>
<f:facet name="header">
<h:outputText value="HEADER" />
</f:facet>
</h:dataTable>
</h:form>
Footer is placed first, but "HEADER" is first displayed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (RF-7371) dropDownMenu: selectedLabelClass isn't applied when you locate on submenu
by Vadim Mikovoz (JIRA)
dropDownMenu: selectedLabelClass isn't applied when you locate on submenu
-------------------------------------------------------------------------
Key: RF-7371
URL: https://jira.jboss.org/jira/browse/RF-7371
Project: RichFaces
Issue Type: Bug
Components: component-menu
Affects Versions: 3.3.2.CR1
Environment: all provided browsers
v.3.3.2-SNAPSHOT
Reporter: Vadim Mikovoz
Assignee: Nick Belaevski
Priority: Minor
Add code to test page:
<rich:dropDownMenu id="dropDownMenuID" value="My Menu"
selectedLabelClass="mySelectedLabelClass">
<rich:menuItem value="1"></rich:menuItem>
<rich:menuItem value="2"></rich:menuItem>
<rich:menuItem value="3"></rich:menuItem>
<rich:menuItem value="4"></rich:menuItem>
<rich:menuGroup value="5">
<rich:menuItem value="item 5.1"></rich:menuItem>
<rich:menuItem value="item 5.2"></rich:menuItem>
<rich:menuItem value="item 5.3"></rich:menuItem>
<rich:menuItem value="item 5.4"></rich:menuItem>
</rich:menuGroup>
</rich:dropDownMenu>, where is
.mySelectedLabelClass{
background-color: red;}
1. Call dropDownMenu --> selectedLabelClass is applied
2. Move mouse over any item in menu popup --> selectedLabelClass is applied
3. Call submenu and move mouse over any submenu item
--------------------------------------------------------------------------------
selectedLabelClass isn't applied
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months