Blog arrows slight bug with arrows

Hi all

I have noticed a slight issue with my recent blog: lichess.org/@/Kingscrusher-YouTube/blog/the-complete-guide-to-chess-opening-principles-king-safety-driven-development/5zEb9Utr - the arrows are not correct when looking at the blog.

You can see the correct arrows if you click the left arrow once under the board and then click the right arrow. E.g. take the diagram under the text "If King safety is the driver, then we can even entertain "undeveloping moves" as this game shows." - the arrow should highlight c6 to b8. The same issue with the next diagram which should be showing b7-b6 pawn move arrow. The next diagram after that should be showing the 4 key central squares. I have checked also on firefox and the Silk browser on my TV and they all seem to have this issue.

Thought I should mention it

Cheers, K

I concur.

Here is more data:

https://i.imgur.com/EwO2kcl.png

The wrong arrow is rendered as:
<g cgHash="720,c6,b8,blue">
<line stroke="#003088" stroke-width="0.15625" stroke-linecap="round" marker-end="url(#arrowhead-b)" opacity="1" x1="1.5" y1="0" x2="2.34375" y2="0"/>
</g>

While the good one is this:
<g cgHash="488,488,c6,b8,blue">
<line stroke="#003088" stroke-width="0.15625" stroke-linecap="round" marker-end="url(#arrowhead-b)" opacity="1" x1="1.5" y1="1.5" x2="2.4301228757031317" y2="3.3602457514062634"/>
</g>

https://i.imgur.com/8zgVIhG.png

First circle is rendered as:
<g cgHash="720,d4,d4,green">
<circle stroke="#15781B" stroke-width="0.0625" fill="none" opacity="1" cx="-0.5" cy="0" r="0.21875"/>
</g>

Correct render:
<g cgHash="488,488,e4,e4,green">
<circle stroke="#15781B" stroke-width="0.0625" fill="none" opacity="1" cx="0.5" cy="0.5" r="0.46875"/>
</g>

That 720 value seems to be everywhere, while the Y value is not written. The Y value in the shape cy attribute is always 0.

Morning TotalNoob69

There is a bug issue note now here: github.com/lichess-org/lila/issues/17418

Maybe you could help solve it - you seem to have a great start already.

Many thanks, K

Seems fixed now - well done lichess :)

Cheers, K