Eduard Bespalov

As workaround I modified xhtml.js - added DOMNodeInsertedIntoDocument handler ``` cXHTMLElement_img.handlers = { "DOMNodeInsertedIntoDocument": function(oEvent) { var aIE = window.navigator.userAgent.match(/MSIE\s(\d+\.\d+)/), bIE9 = aIE && (1 * aIE[1] == 9); if...

The use case is simple - natural attribute names. I wanted to have attributes "on", "off" but I can't. I can't have attributes online, one, onion, onyx etc or any...

Why not to copy browsers behavior? "Standard" events can be handled via inline handlers but not custom events. ``` ``` @onmousemove handles 'mousemove' events but @onxxx does not handle 'xxx'...

You don't realize that an attribute name can't even start from any of this words. I wanted to create attributes 'onLabel', 'offLabel' but I can't. Ok, let's skip "standard" events....

Can't you use lazy evaluation? Until event fires event handler is not created? That's how it works in FF/Chrome.

All attributes including inline handlers should be treated as attributes. But some of them may have **additional** meaning.

At this moment attributes starting 'on-' can be treated in 2 ways. But I agree - without lazy evaluating it will be hard to solve the issue.

When @once attribute is created and **special meaning** is detected **null** event handler is created to handle 'ce' events. When 'ce' event is fired **null** event handler is replaced by...

Check also wire connectors on a board. Just pull gently wires (both - heating bed and hot end wires) I saw ERR7 often when I have had loose connection. Connectors...

I had such issue. It was mechanical problem - a gear on a motor inside an extruder was loose. Use a hex key to tight a fixing screw.