Miro Marchi

Just a comment: I think min and max are useful to normalize the centrality, or that could come as an optional param too.

Hi. I experimented very similar issues with v1.2.2 and v1.3.0. In short, depending on the system date and the desired timezone, there is an issue in handling either the moment...

For example, this case tests the moment before DST kicks in. The original date is written in UTC format, and it is converted to Europe/Rome +01:00. ```js it('should handle DST...

Also, isn't this issue very similar to the one that should be fixed in #108 and #93?

Sure, thanks. This is a simplified version of a one-node visualization. Node is a group containing circle, text and image with mask. ```html Node title ```

Hi. thanks for replying. I switched to a very different way of having the images, so I am not generating from svg anymore. But, for this issue's sake, here is...

Thank you! I just added ```javascript .attr('xmlns', 'http://www.w3.org/2000/svg') .attr('xmlns:xlink', 'http://www.w3.org/1999/xlink') ``` to the svg. Is what you meant? No changes though.

I think this is a real problem. Even Zulu/offset and UTC are considered not identical instants, even if the point in time is clearly the same. I added this case...

Thanks for this information. I will add more comments when I have more time, but for now I just want to address the main topic, your point n. 6 >...

I understand this is not a bug but a designed behaviour. In terms of feature requests, what about some solutions like: - new temporal operators that specifically work on point-in-time...