var manual = '.... use chrome...';

User: "Hey this thing is broken, can you fix it?"
Me: "Works just fine for me, what browser are you using?"
User: "Edge, why?"

..... god I hate browsers.... rtfm bitch.. make my life easier please?...
Sometimes I wish I only did back end work...

why does it only work in chrome? :P

@jonjoe
Cause browsers implement the standards in their own way and time so not every browser behaves the same. In this particular case if you slide a fader knob in my UI dragging the cursor below the window border in ff, and ie/edge it causes the main page to scroll up and reveal a black space about 40px tall across the bottom... but not in chrome!.... :/

but it's a constant struggle.. spreading far and wide

I get that but you shouldn't be having as much as a problem as this. if you need a hand I'm free this weekend :)

It's a work project so I can't really accept the help(but appreciate the offer), and honestly it's pretty much all CSS problems, occasional issue with js methods not being there in IE but majority css.

Pretty much everything can be solved with flags. Throw your CSS in here https://autoprefixer.github.io.

general rule of thumb is don't use CSS properties that are not supported but do use CSS properties that have comparability flags. Use this to guide you http://caniuse.com/#feat=flexbox.

Hope it helps <3

As back-ender, oh yeah, I love not having to deal with that kinda stuff!

@jonjoe
Thanks, I hadn't heard of that auto prefixed before, I'll give it a shot. I prefer backend lower level stuff so css isn't my strong suit, I touuch it rarely and with rubber gloves and a cloths pin on my nose..

I'm full stack, took me over 1000 hours for CSS to become intuitive to me haha. Feel free to nudge me on twitter @thedigitaldinlo or email jonjoe@indee.io if you need discrete help :)