[ https://issues.apache.org/jira/browse/TRINIDAD-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728297#action_12728297 ]
Mamallan Uthaman commented on TRINIDAD-1507: -------------------------------------------- Since name attributes are the same as id attributes, we can safely stop rendering name attributes without affecting the functionality of the application. But, currently, Trinidad doesn't have a mechanism to enable developers to optionally turn-on or turn-off the rendering of name attributes. Also, in the case of basic HTML browsers for which no JavaScript file will be delivered, rendering name attributes is mandatory since parameter name and value pairs are encoded in name attributes. > Do not render name attributes for components to reduce response size for > mobile > -------------------------------------------------------------------------------- > > Key: TRINIDAD-1507 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1507 > Project: MyFaces Trinidad > Issue Type: Improvement > Components: Components > Affects Versions: 1.2.12-core > Environment: all > Reporter: Dave > > To reduce http response size, all components' name attributes should be > removed since they are the same as id attributes. In our app, since many > levels of subview and table/iterators, id/name can be very long, over 100 > characters. > > Removing name attributes can reduce response size by 20%. > This is important for mobile devices. > A flag allows user to optionally render name attributes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.