The original ICEmobile strategy for native components was to use the ICEmobile-SX or container registration flag to determine whether, say, a button with ice.mobi.camera vs an <input type=file> would be rendered. This is now complicated by two factors: the BridgeIt registration mechanism is in-browser only (does not rely on a message to the server, since an HTML application may not have a stateful server) and non-JSF applications should benefit from the fallback.
The new strategy will be to render a button (via a link or a button) and replace it visually with a file input.
New Feature
Major
The original ICEmobile strategy for native components was to use the ICEmobile-SX or container registration flag to determine whether, say, a button with ice.mobi.camera vs an <input type=file> would be rendered. This is now complicated by two factors: the BridgeIt registration mechanism is in-browser only (does not rely on a message to the server, since an HTML application may not have a stateful server) and non-JSF applications should benefit from the fallback.
The new strategy will be to render a button (via a link or a button) and replace it visually with a file input.