I did in the most recent instance of this…
Is this answer in relation to only my 1st question about having “active
(live:) macros”, or is it also in in relation to my 2nd question about “those
(live:) macros updating the content”?
(click:) family of macro need to wait until after the current page has been updated with all the HTML elements being generated by the content of the current Passage before it can scan the whole of the HTML contents of current page to find all instances of the
(click:) macro’s associated target hookname or “text”.
This scanning process may need to be re-done each time the HTML content of the page is dynamically changed by the current passage, like the changes done by an active
(live:) macro. Both the scanning process and the execution of the (live:) macro’s associated hook interfere with an end-user’s ability to interact with the current page, and both can result in unwanted visual effects on the current page.
The above behaviours is one of the main reasons why:
a. it is strongly recommended that you use the (link:) related macros instead whenever possible.
b. to only have a single (live:) macro active at any one time.
I would need to know more about your code to be able to suggest a work around for your specific issue.