incubator-adffaces-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Blake Sullivan <blake.sulli...@oracle.com>
Subject Re: [jira] Commented: (ADFFACES-266) goButton on PDAs should be rendererd as a linked button and not a button
Date Fri, 11 May 2007 17:44:09 GMT
Jeanne Waldman (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/ADFFACES-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495100
] 
>
> Jeanne Waldman commented on ADFFACES-266:
> -----------------------------------------
>
> Yes, but what about all the devices that do not support JS? You've changed "a" to "input"
for everything, not just for PDA.
>   
I completely agree with Jeanne.  The question is why doesn't:

 protected boolean useButtonTags(RenderingContext arc)
  {
    return (supportsScripting(arc) &&
            supportsAdvancedForms(arc) &&
            supportsIntrinsicEvents(arc));
           
  }

return true for your PDA?

-- Blake Sullivan
>   
>> goButton on PDAs should be rendererd as a linked button and not a button
>> ------------------------------------------------------------------------
>>
>>                 Key: ADFFACES-266
>>                 URL: https://issues.apache.org/jira/browse/ADFFACES-266
>>             Project: MyFaces ADF-Faces
>>          Issue Type: Improvement
>>         Environment: PDA
>>            Reporter: Piyush Hari
>>            Priority: Minor
>>         Attachments: patch_oct27_05_33PM_goButton_pda.patch
>>
>>
>> At present the following logic in GoButtonRenderer renders a goButton as a LINK (html
'a' tag) on PDAs because they don't support button tag :
>>  
>> String element = useButtonTag ? "button" : "a";
>>  
>> I wonder why a link is renderered when browsers that don't support 'button' tag *CAN*
support 'input' tag of type 'Button'.
>>     
>
>   


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message