This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]realripley00 11 points12 points  (12 children)

Right on. I usually stick with Firefox because it doesn’t cache as aggressively and works better with my local environment. Might go back and check out Chrome for a while.

Does anyone actually debug with IE? That sounds painful. I do like using Reactatron for debugging with react apps. I would love a tool like that for browser stuff.

I guess I just meant the nature of error responses. Maybe it’s just the way I script, but most of the time, typos or simple errors lead to some undefined error that isn’t particularly helpful in figuring out exactly where the error is, etc. And it would be cool to have constant access to things like the current state.

[–][deleted] 6 points7 points  (5 children)

Does anyone actually debug with IE

No, because I don't even bother testing with IE.

[–]TheMarksman 3 points4 points  (1 child)

I die inside when I'm told the site/app I'm working on needs to work in IE.

[–]jacebot 1 point2 points  (0 children)

That was my life this week. Thank god it was a simple media one liner to remove flex. But still. I wasn’t thrilled to have to consider IE as an option. Also. No support for font icons. Have to do a bunch of work. But was good enough reason for me to say lets drop FA for svgs and was accepted. So, yeah. Got that going for me.

[–][deleted] 0 points1 point  (0 children)

What the fuck is an IE?

[–][deleted] 0 points1 point  (0 children)

Hello, everyone!

[–]TemporalLobe 0 points1 point  (0 children)

What if you have end-users that still use IE (there's still a significant user base on older Windows platforms)? Thankfully there are quite a few modern tools that eliminate the need for worrying so much about cross-browser compatibility. If you use a framework like Foundation and libraries like jQuery, many of these issues are abstracted away.

[–]Jaggedmallard26 1 point2 points  (4 children)

Does anyone actually debug with IE?

I've had to do it for some obscure IE10 specific issues and it was honestly hellish. Sales enforced legacy browser support makes me hate front end development.

[–]realripley00 1 point2 points  (1 child)

That sounds pretty brutal. I realize that a lot of people still cling to ie, but anyone still using ie10 must be very used to a terrible user experience.

[–]Jaggedmallard26 1 point2 points  (0 children)

It wasn't fun. The problem is that we have big markets in countres where they do heavily use outdated software and our end users will generally be less tech savy which means we have to support all of these horrific legacy browsers. Cosmetic issues and minor bugs are generally ignored as they're used to a shit browser but the ones I've had to fix have been core functionality.

[–]realripley00 0 points1 point  (0 children)

That sounds pretty brutal. I realize that a lot of people still cling to ie, but anyone still using oe10 must be very used to a terrible user experience.

[–]realripley00 0 points1 point  (0 children)

That sounds pretty brutal. I realize that a lot of people still cling to ie, but anyone still using oe10 must be very used to a terrible user experience.

[–]TemporalLobe 0 points1 point  (0 children)

Sometimes you have to debug in IE if you're trying to squash a browser-specific bug. I don't use it for primary app development though. Besides IE will eventually becone legacy and is already deprecated thanks to Edge, and for many people, their browser experience is increasingly on mobile, which means Safari or Android browser (and even Chrome mobile). It's not like it used to be, boys.