Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internet Explorer support #74

Closed
talha131 opened this issue Nov 17, 2013 · 9 comments
Closed

Internet Explorer support #74

talha131 opened this issue Nov 17, 2013 · 9 comments
Labels
pull request welcome Not a priority right now, but if you provide a pull request, we would merge it.
Milestone

Comments

@talha131
Copy link
Member

I haven't tested Elegant on any version of Internet Explorer. If you find any problem with Elegant on Internet Explorer, please feel free to submit a pull request.

@calfzhou
Copy link
Contributor

Elegant looks a little ugly on IE. But, well, i'd rather to add a warning message to tell visitors use a better browser 😆

Anyway, it's time to update bootstrap version, we are still using 2.x.

image

@talha131
Copy link
Member Author

We should not bind internet explorer support with Bootstrap3 integration.

@calfzhou
Copy link
Contributor

Today i tried IE 10 on my Win7, most things work fine.

The problem I mentioned above seems only occurs on IE10 with Win8. Here is the solution suggested by bootstrap official site (http://getbootstrap.com/getting-started/#ie-10-width). I tried it, but still cannot fix it. Need more investigation.

@talha131
Copy link
Member Author

Argh! Front end design is surely a tough nut to crack because of all these nuances. Thank you for attempt! Hope you will find a solution soon.

@silverhook
Copy link
Member

As IE is end-of-life, is this still relevant?

https://en.wikipedia.org/wiki/Internet_Explorer#End_of_life

@talha131
Copy link
Member Author

Personally I think we shouldn't care much about supporting IE or older browser versions. This will let us use latest features like CSS-Grid which isn't supported on older browsers.

Supporting old browsers is too much work. I say we close this issue.

@silverhook
Copy link
Member

silverhook commented Dec 28, 2018

I agree.

I would say the order should be:

  1. W3C compliance as a must
  2. Blink (Chromium) support
  3. Gecko (Firefox) support
  4. text-based browsers (Lynx, Elinks, W3) support
  5. WebKit (Safari, Qt- and GTK-webkit, Opera, new Edge) support

Personally, I prefer Firefox to Chromium, but the market share is the other way around, so that makes more sense.

@iranzo
Copy link
Member

iranzo commented Jan 13, 2019

@talha131 talha131 added this to the 2019 - Q2 milestone Jun 17, 2019
@talha131
Copy link
Member Author

IE is ancient history. Even MS has moved from it.

Considering the size of the team, we can't afford to have support for legacy browsers.

Also, we plan to use CSS grids and Flexbox in the theme which is not going to work on IE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pull request welcome Not a priority right now, but if you provide a pull request, we would merge it.
Development

No branches or pull requests

4 participants