Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Demo does not work in IE8 #107

Closed
aokolish opened this Issue · 12 comments

5 participants

@aokolish

After having issues getting flexslider to work in IE8, I noticed that your demo doesn't seem to work in IE8 either. There doesn't seem to be a javascript error on the page, but the spinner just spins forever.

http://www.woothemes.com/flexslider/flexslider-demo/

@jacobcoens

There are, in fact, several JavaScript errors.

@mbmufffin
Collaborator

Hmm, I can't attest for the JavaScript errors on WooThemes, but you can check out my demo over here, fully functional down to IE7:

http://flex.madebymufffin.com/demo/index.html

@aokolish

Yeah, you're right about that one working. I was wondering what happened to your old site. Well, you're the author/maintainer; do whatever you want with this info. I suspect my issue is something else.

@mbmufffin
Collaborator

Whenever I have problems in IE, I check for possible syntax errors, such as trailing commas or redundant jQuery includes. You ever solve your issue?

@jasongonzales23

The issue we are having is visible on the home page, uppermost slideshow here: http://cpiadmin.webfactional.com. There are two instances of Flexslider on the page, but he JS couldn't be anymore straightforward. Just bombs in IE.

@stevetauber

Windows Phone 7 (WP7) also fails.

@jasongonzales23

Well, we just discovered the problem in our application of FlexSlider was our fault. Small markup error. You can close the ticket.

@mbmufffin
Collaborator

Can you describe how it fails on WP7?

@mbmufffin
Collaborator

Care to share what your issue was, Jason? Could help me pass on knowledge to future users with IE issues. I took a quick glance at your setup and didn't see anything glaringly wrong.

@stevetauber

The example doesn't load. It just shows the spinner. I'll research it about more in the coming weeks. Feel free to close this ticket and if need be I'll open a more specific WP7 one at a later date.

@jasongonzales23

Of course, the markup that somehow got botched looked like this (its a Django template):

 <li>
      <a href="#">
        <img src="{{MEDIA_URL}}{{ slide.slide }}" alt="{{ slide.caption }}"/>
      </a>
      <div class="slide-text">
    <h2 class="{{slide.headingColor}}">
            {% if slide.heading_1 %}
              <span class="description">{{ slide.heading_1}}</span>
            {% endif %}
            {% if slide.heading_2 %}
              <span class="product">{{ slide.heading_2}}</</span> <!-- notice the double closing marks there -->
    </h2>
    {% endif %}
    {% if slide.caption %}
    <p class="caption {{ slide.captionColor }}">
    {{ slide.caption }}
    </p>
    {% endif %}
    {% if slide.buttonText %}
      <a href="{{ slide.buttonLink }}" class="cta">{{slide.buttonText}}</a>
    {% endif %}
      </div>
    </li>

So, if its not obvious, the problem is that everything but IE fixed our bad markup, so you can't see it when inspecting in-browser. Nothing that days and days of staring blankly at your own code won't fix!!

@mbmufffin
Collaborator

Haha, love it when that happens. Cheers, Jason, and thanks for sharing.

@mbmufffin mbmufffin closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.