Replies: 1 comment
-
The difficulty with the content security policies were easily resolved, and it is a regret this thread was not updated sooner to reflect it. Development of the module to integrate Hinode with TimelineJs has been a struggle from the start, and will be abandoned. Inevitably, achieving consistent rendering was the biggest hurdle to overcome. Everything would render perfectly on the "examplesite", but when used in a production build, the module would cease to render anything at all or would render the viewport according to the position of the mouse cursor. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Attempted to develop module for Hinode allowing use of timelinejs as a shortcode. Required parameter being the JSON file containing the data from the timeline and an optional ID for the timeline container element.
The development of this module has been a struggle due to encountering numerous issues with content security policy. What made these issues difficult was the absence of obvious observable feedback through normal channels. Complicating matters is the timelinejs package itself, which relies heavily on external resources to provide features already handled by Hinode itself.
Currently examining what options are available, and reviewing documentation further.
My repository is here: Hinode mod-timelinejs3
Beta Was this translation helpful? Give feedback.
All reactions