-
I have a marko tag with the following marko-tag.json:
```
{
"@class" : "string",
"@items []": {
"@wallpaper ": {
"@class": "string"
},
"@panel ": {
…
-
For progressive rendering, I tried to use `` and moved the `` to the top of HTML, but unfortunately it didn’t work. The Widgets are initialized after the DOM ready event, instead of the end of async f…
-
The below line is not working in marko5 and I have tested the `$(document).append()` in some other pages and It is working fine . I think Marko interrupt this append method. Kindly let me know If you …
-
Most renderers look similar to this:
``` javascript
var template = require('marko').load(require.resolve('./template.marko'));
module.exports = function(input, out) {
template.render(input, out);…
-
Per email thread:
We probably need to look into a better way to prevent the same taglib from being loaded multiple times, but currently the Marko compiler walks up the directory tree to find taglibs …
-
Right now, when a template is bound to a widget but the renderer and widget logic is split, there is an additional function:
```
function __registerWidget() {
if (typeof window != "undefined") {
…
-
When our renderer.js looks like the following:
``` javascript
module.exports = require('marko-widgets').defineRenderer({
// ...
});
```
It will correctly render the given component but then end …
-
Page does not work the first time after the server is started, but works after this initial load.
-
This can lead to EventEmitter memory leak warnings (even though it is not really a memory leak) since shared EventEmitters may receive a lot of `destroy` listeners.
This is the reason for https://git…
-
I have found that giving an empty array to a state property in the `getInitialState()` method always tricks stateful widgets into a re-render even if none of the given state properties changed...
Par…