[JBoss JIRA] Assigned: (RFPL-930) Calendar test automation: cover all attributes
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RFPL-930?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RFPL-930:
----------------------------------
Assignee: Ján Jamrich (was: Pavol Pitonak)
> Calendar test automation: cover all attributes
> ----------------------------------------------
>
> Key: RFPL-930
> URL: https://issues.jboss.org/browse/RFPL-930
> Project: RichFaces Planning
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: QE
> Reporter: Pavol Pitonak
> Assignee: Ján Jamrich
> Fix For: 4.Future
>
>
> Create Selenium tests for following attributes of rich:calendar:
> * converterMessage
> * currentDate
> * dataModel
> * dayEnabled
> * direction
> * hidePopupOnScroll
> * horizontalOffset
> * immediate
> * jointPoint
> * minDaysInFirstWeek
> * mode
> * monthLabels
> * monthLabelsShort
> * preloadDateRangeBegin
> * preloadDateRangeEnd
> * required
> * requiredMessage
> * resetTimeOnDateSelect
> * tabindex
> * timeZone
> * todayControlMode
> * validatorMessage
> * value
> * verticalOffset
> * weekDayLabels
> * weekDayLabelsShort
> * zindex
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Moved: (RFPL-1498) Component reference: remove a4j:form
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RFPL-1498?page=com.atlassian.jira.plugin.... ]
Jay Balunas moved RF-11001 to RFPL-1498:
----------------------------------------
Project: RichFaces Planning (was: RichFaces)
Key: RFPL-1498 (was: RF-11001)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: 4.0.0.Final
(was: 4.0.0.Final)
Component/s: doc
(was: doc)
Fix Version/s: 4.1.0.Milestone1
(was: 4.1.0.Milestone1)
> Component reference: remove a4j:form
> ------------------------------------
>
> Key: RFPL-1498
> URL: https://issues.jboss.org/browse/RFPL-1498
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.0.0.Final
> Reporter: Pavol Pitonak
> Fix For: 4.1.0.Milestone1
>
>
> The component reference contains <a4j:form> on several places. Use <h:form> instead of <a4j:form>:
> section 9.4.2. Showing and hiding the pop-up
> section 9.4.5. Header and controls
> section 13.4.2. Attaching the tool-tip to another component
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Moved: (RFPL-1495) popupPanel: documentation omits forms requirement and contains wrong sample
by Jay Balunas (JIRA)
[ https://issues.jboss.org/browse/RFPL-1495?page=com.atlassian.jira.plugin.... ]
Jay Balunas moved RF-11065 to RFPL-1495:
----------------------------------------
Project: RichFaces Planning (was: RichFaces)
Key: RFPL-1495 (was: RF-11065)
Workflow: jira (was: GIT Pull Request workflow )
Affects Version/s: 4.0.0.Final
(was: 4.0.0.Final)
Component/s: doc
(was: doc)
Fix Version/s: 4.1.0.Final
(was: 4.1.0.Final)
> popupPanel: documentation omits forms requirement and contains wrong sample
> ---------------------------------------------------------------------------
>
> Key: RFPL-1495
> URL: https://issues.jboss.org/browse/RFPL-1495
> Project: RichFaces Planning
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.0.0.Final
> Reporter: Ilya Shaikovsky
> Priority: Critical
> Fix For: 4.1.0.Final
>
>
> http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/ht...
> 1) That note:
> "Placement
> The <rich:popupPanel> component is usually rendered in front of any other objects on the page. This is achieved by attaching the component to the <body> element of the page, and setting a very high "z-index" (t"
> actually have to be followed by one more critical note.
> "Limitation: defined by default popup *has to* have form element inside and not to be nested to external form in order submitting components/behaviors inside to work properly (because of repositioning in DOM). And to be able to be nested domElementAttachment should be changed to either form or parent."
> 2) Example 9.2. <rich:popupPanel> example
> confuses as form is around the panel! it should be either removed at all(as that sample not requires submission) or moved inside.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months