Skip to content
This repository has been archived by the owner on May 1, 2020. It is now read-only.

Internet Explorer 11 click-block div prevents clicking #203

Closed
alfabetagama opened this issue Oct 20, 2016 · 6 comments
Closed

Internet Explorer 11 click-block div prevents clicking #203

alfabetagama opened this issue Oct 20, 2016 · 6 comments

Comments

@alfabetagama
Copy link

Short description of the problem:

When building for release Internet Explorer displays click-block div element in front of application content. This element prevents any interaction with application. This DOES NOT happen in development mode.

What behavior are you expecting?

I expect buttons to be clickable and inputs to be able to accept input.

Steps to reproduce:

  1. Create app with menu and page
  2. Place button on a page
  3. Build with --release switch
  4. Run in IE 11
  5. try to click the buitton

Which @ionic/app-scripts version are you using?
ionic-app-scripts 0.0.36

Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)

Fix:

//IE
@media all and (-ms-high-contrast: none), (-ms-high-contrast: active) {
    .click-block {
        display:none;
    }
}
@WhatsThatItsPat
Copy link

IE isn't supported.

@alfabetagama
Copy link
Author

@PatrickMcD I didn't find any official documentation regarding the IE non-support, however apart from some minor styling bugs it works just fine. And of course the click-block div.

@WhatsThatItsPat
Copy link

It might not be in the official docs, but there are some comments scattered throughout the issues about it.

ionic-team/ionic-framework#8669 (comment)
ionic-team/ionic-framework#6386 (comment)

etc...

@danbucholtz
Copy link
Contributor

@jgw96 can you move this.

Thanks,
Dan

@jgw96
Copy link
Contributor

jgw96 commented Oct 20, 2016

This issue was moved to ionic-team/ionic-framework#8828

@jgw96 jgw96 closed this as completed Oct 20, 2016
@jgw96
Copy link
Contributor

jgw96 commented Oct 20, 2016

Hello @alfabetagama , thanks for opening an issue with us! Since this issue is an issue with the framework and not app-scripts i have moved this issue to the appropriate repo. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants