Not sure if it is worth looking into it, though this evening I downloaded the Win10 VM with Edge and noticed the home and community buttons are apparently broken at mobile sizes.
It is, especially since a lot of users have taken advantage of free upgrade. And not everyone shifted to FF 40 / Chrome.
@emanuele, I am on Win10 and opened up Edge to see how it looked. I shrunk it down to the minimum size and I don't see the same thing. Maybe your cache was messed up? I don't have a Win10 phone to test it on a real mobile but I don't think that's going to make a difference here.
I was using the virtual machine, so it may just some missing stuff there. If it looks good on a real one that's good enough to me! :D
same on regular Win 10 with Edge:
(http://i.imgur.com/XEvd00C.png)
MS Edge 20.10532.0.0
I have second PC with exactly the same config and it looks good there ::)
.... meh...
Weird, on my Windows 10 and MS Edge everything looks fine.
xD
Is it messed up on the community page as well? Only the home page has the added bootstrap css and if thats causing the conflict we can figure it out.
This i have used for my startpage from bootstrap
ElkArte default
/*!
* Bootstrap v3.3.5 (http://getbootstrap.com)
* Copyright 2011-2015 Twitter, Inc.
* Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
*/
/*! normalize.css v3.0.3 | MIT License | github.com/necolas/normalize.css */
h1,
h2,
h3,
h4,
h5,
h6,
.h1,
.h2,
.h3,
.h4,
.h5,
.h6 {
font-family: inherit;
font-weight: 500;
line-height: 1.1;
color: inherit;
}
h2,
.h2 {
font-size: 30px;
}
.container-fluid {
padding-right: 15px;
padding-left: 15px;
margin-right: auto;
margin-left: auto;
}
.clearfix:before,
.clearfix:after,
.container-fluid:before,
.container-fluid:after,
.row:before,
.row:after,
.panel-body:before,
.panel-body:after {
display: table;
content: " ";
}
.clearfix:after,
.container:after,
.container-fluid:after,
.row:after,
.pager:after,
.panel-body:after {
clear: both;
}
.col-md-1, .col-md-4, .col-md-7, .col-md-8, .col-md-10 {
position: relative;
min-height: 1px;
padding-right: 15px;
padding-left: 15px;
}
.panel {
margin-bottom: 20px;
background-color: #fff;
border: 1px solid transparent;
border-radius: 4px;
-webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, .05);
box-shadow: 0 1px 1px rgba(0, 0, 0, .05);
}
.panel-body {
padding: 15px;
}
.panel-default {
border-color: #ddd;
}
.well {
min-height: 20px;
padding: 19px;
margin-bottom: 20px;
background-color: #f5f5f5;
border: 1px solid #e3e3e3;
border-radius: 4px;
-webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, .05);
box-shadow: inset 0 1px 1px rgba(0, 0, 0, .05);
}
.row {
margin-right: -15px;
margin-left: -15px;
}
.lead {
margin-bottom: 20px;
font-size: 16px;
font-weight: 300;
line-height: 1.4;
}
.img-thumbnail {
display: inline-block;
max-width: 100%;
height: auto;
padding: 4px;
margin-right: 5px;
line-height: 1.42857143;
background-color: #fff;
border: 1px solid #ddd;
border-radius: 4px;
-webkit-transition: all .2s ease-in-out;
-o-transition: all .2s ease-in-out;
transition: all .2s ease-in-out;
}
/* This one does up to 540 screens. */
@media screen and (max-width: 33.750em) {
.fa-15x {
font-size: 1.0em;
line-height: 0.75em;
vertical-align: -15%;
margin-top: 0.005em;
}
h2, .h2 {
font-size: 25px;
}
.column {
font-size: 0.85em;
}
}
@media (min-width: 768px) {
.lead {
font-size: 21px;
}
}
@media (min-width: 992px) {
.col-md-1, .col-md-4, .col-md-7, .col-md-8, .col-md-10 {
float: left;
}
.col-md-10 {
width: 83.33333333%;
}
.col-md-8 {
width: 66.66666667%;
}
.col-md-7 {
width: 58.33333333%;
}
.col-md-4 {
width: 33.33333333%;
}
.col-md-1 {
width: 8.33333333%;
}
}
I'll check it out this evening when I'll boot the VM. :D
Yep. Not a Elk bug but a site bug