alexlii
(Alex)
October 19, 2019, 3:35am
19
Hi Jim,
Thanks anyway, that is definitely a great way.
By the way, I found the way of triggering by Unique Element ID might be quite limited, and the way by class name seems quite flexible.
and I am just thinking the possibility of the way of changing "fixed" to absolute" and absolute to fixed by hypeDocument.setElementProperties
, and I found an interesting case here:
↑ extension index
hypeDocument.setElementProperties
Sets multiple properties in one go (with the optional possibility to animate them)
[20180412-dj7ka]
/**
* setElementProperties v1.1
* @param {Element} target to be animated
* @param {Object} object with properties to be animated
* @param {Number} time in seconds for no animation (optional)
* @param {String} easing function (optional)
*/
hypeDocument.setElementProperties = function ( target, obj, duration, ease) {
for (var prop in ob…
↑ extension index
hypeDocument.setInnerHtmlByClass
Sets all the all elements of a given class to the content one provides. Usefull to update content across scenes and layouts all at once. Elements that want to subscribe to content updates only need to be assigned the associated class
Reasons for using class based targeting over ID based targeting:
Hype has a unique approach when it comes to responsive layouts. As with scenes themselves it keeps them in own HTML braches. Meaning when you ha…
and I will study more, and thanks again.