The-M-Project
The-M-Project copied to clipboard
mwaylabs
'The-M-Project' is a Mobile HTML5 Application Framework.
The text field updates its value from DOM only on keyup. This prevents an autocomplete via a tap/click event to not correctly populate the value of the text field. Shouldn't...
Based on the proxy definition in config.json M.Request should have the functionality to automatically decide between direct URL or proxy URL whether the app's running in a container or web...
When defining a back-button in the ToolBarView, the getCurrentPage() method in M.ViewManager is returning the wrong view. This is because the event on the back-button is defined as such: ```...
Please extend the documentation for "native packaging" (http://panacodalabs.github.com/The-M-Docs/#espresso/native_packaging) with Android-specific details. Especially, when Espresso's pull request 87 (https://github.com/mwaylabs/Espresso/pull/87) gets accepted, an extra section for AndroidManifest.xml manipulation and a reference to...
The action sheet dialog doesn't render to the correct position on a scrollable page. If, for instance, you are scrolled to the bottom of a page, the dialog will render...
If you use a childview with a toolbar the showBackButton does not work. I tested it with both just a label and with a button in the childview and added...
Right now, if you want to have different event types being bound to one handler, you have to write duplicated code like this: ``` javascript events: { tap: { target:...
If you include a Toolbar with child items in a header or footer or if you include items by themselves or as a group of items kind of like a...
It appears that if you include a button on more than one view the event is only registered with one view and therefore the button does not work and does...