[richfaces-planning-issues] [JBoss JIRA] (RFPL-2499) Placeholder Component to QE testing prep

[Jiří Štefek (JIRA)]

     [ https://issues.jboss.org/browse/RFPL-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiří Štefek reassigned RFPL-2499:
---------------------------------

    Assignee: Lukáš Fryč  (was: Jiří Štefek)


Added component to Metamer.
Provided some samples, not sure if the csv samples should be made for all input components.
I have not used any workarounds.

Bugs:
I've noticed that there is no placeholder displayed in rich:inplaceInput. 
In rich:inplaceSelect there is also no placeholder displayed, but when you click in this component and then outside without selecting anything, the placeholder will display. 

Another bug I've noticed is, when there is attribute @selector present in component without any value (empty), placeholder will not work.

In rich:editor the placeholder will not disappear after focusing the editor. Is it possible to show/hide the placeholder there?

How should this component behave, when you submit a form with some input component (e.g. inputText with placeholder) with a4j:commandButton? Should the placeholder text be submitted (now it is submitted) or not?

Should I report these issues, or is it enough for you to have them here?
                
> Placeholder Component to QE testing prep
> ----------------------------------------
>
>                 Key: RFPL-2499
>                 URL: https://issues.jboss.org/browse/RFPL-2499
>             Project: RichFaces Planning
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: QE
>    Affects Versions: 4.3.0.M3
>            Reporter: Lukáš Fryč
>            Assignee: Lukáš Fryč
>             Fix For: 4.3.0.M3
>
>
> The component has been introduced to core frameowork,
> it still have some issues (with known workarounds) to be addressed, see RF-12563.
> Dev-example is available.
> It's important to verify this component with various components  generating text inputs:
> * inputText
> * inputTextarea
> * calendar
> * inplaceInput
> * inplaceSelect
> * select
> * editor
> * client-side validated input
> Some of them won't likely work, but we need to identify those first.

--
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