search

salsita / jq-clipthru

89 stars 12 forks source link

Scroll bug in Safari #4

Closed tldrRD closed 6 years ago

tldrRD commented 6 years ago

When the position of the element is fixed, the element starts to jump around, something like a glitch effect on element position. Maybe this is happening because of the partial support of the clip property? After some research I learned that the clip property is deprecated: https://developer.mozilla.org/en-US/docs/Web/CSS/clip

ghost commented 6 years ago

Hi @NulledGravity clip is deprecated, but unlike other options it has and will continue to have 100% support in the near future. There is a lot at play to get the effect, so I'm thinking it could be something specific to your usecase, perhaps a styling conflict. Is there some way to see the issue you're having (ideally so I could inspect the DOM)? Does it only happen in Safari in your case? You should be seeing the same issues on the demo page: http://salsita.github.io/jq-clipthru/demo/

tldrRD commented 6 years ago

Hey @mystrdat, thanks for your response. Here is a quotation from the MDN 'clip' documentation page:

Though some browsers may still support it, it is in the process of being dropped. Avoid using it and update existing code if possible;

Regarding the demo, it works as intended in Safari. I guess you are right and it's a specific problem related to my DOM. I will further inspect it and let you know if I manage to find something.

ghost commented 6 years ago

Hey @NulledGravity , the process of being dropped is IMHO a process where the feature will practically stay for decades, because there's no good reason to break it on existing websites that use it. There are overall many similar leftovers conserved by time for compatibility purposes, like <marquee> (already obsolete status, yet still works everywhere). I think we have at least a few years before the first browser removes clip support, if at all. I was thinking of rewriting the library with clip-path (and no jQuery among others), but that approach has other drawbacks (clipped areas are still interactable). Anyway, let me know if you happen to find the conflict, I'm interested if it's something I could help solve in the implementation.

ghost commented 6 years ago

Closing due to inactivity.