The epic event-driven browser language for UI with functionality in one-liner CSS. Over 100 incredible CSS commands for DOM manipulation, ajax, reactive variables, single-page application routing, and lots more. Could CSS be the JavaScript framework of the future?
Getting the property id of the body node returns a type of "string" even when not explicitly set, which breaks inherited attribute replacement in the core because it thinks an id property is actually there. An id property must be being set internally in the browser.
I've split up the attr and prop return function as it was falling back to getting the property when it wasn't actually being asked for - which is unnecessary, and put in a better check for attribute existence, and the fix is now on the branch.
This fix will definitely need testing on a variety of production code before official release.
bob2517
commented
9 months ago
Getting the property id of the body node returns a type of "string" even when not explicitly set, which breaks inherited attribute replacement in the core because it thinks an id property is actually there. An id property must be being set internally in the browser.
I've split up the attr and prop return function as it was falling back to getting the property when it wasn't actually being asked for - which is unnecessary, and put in a better check for attribute existence, and the fix is now on the branch.
This fix will definitely need testing on a variety of production code before official release.