Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Problem with Catch Everest Pro Featured Slider on IE10 #275316
    jstollvt
    Participant

    Hmm… Not sure how to attach a file in the editor here, but here’s a link to a screen capture. As you can see, the “< >” slider control buttons are far down below the image, and a large swath of whitespace is introduced below the slider. In most cases, this resolves itself when the slider automatically moves to the next image, but there have been reported cases where it just sits like that permanently. This seems to be happening primarily on IE10, but I’ve been able to replicate it on other browsers, as noted above.

    Let me know if you’re unable to get to the screen shot, and/or if I can provide any additional information.

    Thanks for the help!

    https://drive.google.com/file/d/1x7mUkhyKxc0kBEfUs1GkUJDloFGpkEL9/view?usp=sharing

    in reply to: Problem with Catch Everest Pro Featured Slider on IE10 #275069
    jstollvt
    Participant

    Thanks for your help, Skandha – the site is https://glycomip.org/

    in reply to: Problem with Catch Everest Pro Featured Slider on IE10 #274345
    jstollvt
    Participant

    Hmm… I’ve been able to reproduce this on Chrome, Brave, and Safari (but not Firefox). The difference with these browsers is that in order to reproduce the problem, I first need to scroll the page to the point where the slider no longer shows on the page. Then, when I do a hard refresh the page, I see the body content render down the page below a blank area, and the slider navigation left/right controls render down in the visible portion of the page (ie, well below the slider area). The delay between this jumbled initial rendering, and it correcting itself happens much more quickly in Chrome, Brave, and Safari, than it does in IE, but it’s still there momentarily. (In reality, it’s unlikely that users will stumble on this particular set of circumstances in most cases, in these other browsers, but if it helps to diagnose what might be going on in the case of IE, I thought I’d share what I’ve found.)

Viewing 3 posts - 1 through 3 (of 3 total)