Face palm, can't use fixed since it's relative to scroll.

I am back, because I have an idea.

Recently the mouse position is decoded from the event's context pageX and pageY, but what if we would use clientX and clientY? Here is a figure explaining the difference.

Can you try it out? The src/Internal/Common/Utils.elm should be modified:

pageX : Json.Decode.Decoder Float
pageX =
    Json.Decode.field "clientX" Json.Decode.float


pageY : Json.Decode.Decoder Float
pageY =
    Json.Decode.field "clientY" Json.Decode.float

@vikfroberg

Awesome, I'll try that out!

Hi @vikfroberg ,

I would like to reopen and merge your PR, because it solves the problem with position: relative parents.

As a workaround when I need to use scroll on parent I usually put the ghost element outside of that parent's scope.

Do you agree on merging your PR?