html5 - Falling back on Android resource values for attribute defaults in a microformat -


i'm designing microformat consumed android client, extract elements containing menu commands , other metadata before pushing remaining content webview.

i embed each menu command json object, like:

<span class="menu-command">{"type": "share"}</span> 

the handler logic implemented natively client, , display properties (title, icon) pulled resource xml.

now i'm considering switching more semantic html5 tags, possibly like:

<menu>   <menuitem label="share" data-type="share">   <!-- other actions --> </menu> 

with data-* attributes other fields required json spec (depending on type of action).

we'd still use android app's resource file default values command's label , icon, i'm not sure of standards-friendly way so; label attribute required, , logic replace value isn't letter of standard, @ least.

is there standards-compliant, or @ least conventional way client replace value of html attribute in fashion?


Comments

Popular posts from this blog

java - Jmockit String final length method mocking Issue -

asp.net - Razor Page Hosted on IIS 6 Fails Every Morning -

c++ - wxwidget compiling on windows command prompt -