Closed uinika closed 5 years ago
Old versions of IE (IE 11 too) not support by Microsoft from January 12, 2016. IE 11 was supported till 2015 year and for now it can't totally show all CSS3 styles (can't show shadow-borders in Gemini, transparents, etc.) and some JS features (sidebar in Pisces/Gemini, TOC, footer alignments).
Miscrosoft suggest to upgrade from IE to Edge, and Edge already support all new features above. image
But if u still want to use IE, u can downdgrade NexT to version to 4.x or try to use any another simple theme with old css styles and without new JS features.
企业实际生产环境当中,前端通常都会要求兼容至IE11,国内Win7 + IE11的用户占据全部PC用户的一半以上,这个是现实国情。如果这个项目总是按照团队偏好尝试使用CSS3的各类新特性,而不考虑最为基本的兼容性(保持布局基本可用,内容完整可见),我确实只能选择使用其它皮肤,毕竟我的博客并不仅仅是写来给拥有新版浏览器的用户阅读的。
Thanks, We'll consider it with discretion.
Maybe it is different between china and world.
I don't understand why IE still un use by peoples...
Some goverment and enterprise still choose IE11, because IE Edge must install Win10 that usually force-autoupdate and upload private info to the MS cloud. obviously, it's not controlled & safe ! Even though Chrome & FF has great user experience, but IE still has a lot of users. Especially some non-professional guys , don't ignore them.
So, can you try to switch to v6 branch and check IE11 compatability?
Also, what actually don't work with current master branch?
unable to display content and layout dislocation
Can you provide screens for this?
You can also check #30 issue, same behaviour?
Nothing to see in IE11, thanks for your attention.
So, can you try to switch to v6 branch and check IE11 compatability?
Just switch branch from master
to v6
:
cd themes/next
git checkout v6.x
And try to repeat same steps.
I always take below command to update my project.
λ git submodule update --remote
So there is no way to specify the exact version. but it works good when i take the checkout v6.7.0
.
I think git submodule
is more elegant than the git checkout
, I suggesstion that push statble release into the master
branch and push development code into the develop
, it should be a best practice.
If you want stable release version, you can read installation guide here: https://theme-next.org/docs/getting-started/installation/
https://git-scm.com/book/zh/v2/Git-工具-子模块 You can go into submodule directory and check out branch I'm using submodule too, and work in custom branch
See this issue https://github.com/theme-next/hexo-theme-next/issues/567 This branching model is also best practice. And gitlab use the similar branching model. https://docs.gitlab.com/ee/university/training/gitlab_flow.html#release-branch I love this!
PLS refer to this article https://nvie.com/posts/a-successful-git-branching-model/, Git Flow more convenient when use with git submodule
.
just sugestion, suit yourself.
I see what title is «IE11 compatibility issue with 6.7.0 Gemini», but we talking about other things.
Issue solved or not? IE work fine?
IE11 works fine when checkout 6.7.0 tag.
But not work with master
branch?
Here is my blog about git-flow Also referred to Vincent Driessen's branching model. I don't like Vincent Driessen's branching model, duo to it maybe cause error when the operator is not careful
@ivan-nginx
Yep, there seems to be a problem with the master
branch, U can see my screenshot above.
@uinika master
branch as v7.x
deploy branch, it no longer supports ie
@uinika fix will soon, wait a little.
@uinika check master
branch now (update it).
Thanks for your help.
Expected behavior
Browser compatibility bug for IE11.
Actual behavior
Open the hexo-theme-next 6.7.0 website with IE11, unable to display content and layout dislocation.
NexT Information
NexT Version:
NexT Scheme: