>Instead, that client is using IE6, doesn't know how to tell you that, and IT restrictions prevent them from upgrading or using another browser.
At least _I_ personally can do something about it, instead of grasping at straws and begging someone else to do something right on their end. If they want to use IE, fine, but they only get IE supported features and everything cost 10x as much, win-win.
>Or they have Chrome and a shitty addon that breaks your site in a way that you can't even imagine.
Dealt with this repeatedly,"sir, try Firefox, it works there? Great, use that instead, or remove the Chrome plugins."
I had a client that was in the Beta channel of chrome and had some obscure bug causing her issues, but no one else. I figured that out just fine.
Just last week a client had the stupid Grammarly plugin wreck something online, fixed in minutes.
>Or they are behind a workplace firewall that blocks some specific ___domain used by the site.
Say, "Call your tech support guys, I am unable to fix that." I can't say that to a guy that is holding only a CD that got mailed to him, because I am the only support then.
>I've done support for a webapp, and I've had to use remote desktop sharing quite a few times.
Yep, and in the near future this will work in the browser, we are close now. And the beauty of the internet is that if they don't have access, we don't have to debug until they do. (their ISPs/intranet problem) But in the old days, it didn't matter what the issue was, and if the computer was not online, then the only data I could get to debug from was irate staff.
At least _I_ personally can do something about it, instead of grasping at straws and begging someone else to do something right on their end. If they want to use IE, fine, but they only get IE supported features and everything cost 10x as much, win-win.
>Or they have Chrome and a shitty addon that breaks your site in a way that you can't even imagine.
Dealt with this repeatedly,"sir, try Firefox, it works there? Great, use that instead, or remove the Chrome plugins."
I had a client that was in the Beta channel of chrome and had some obscure bug causing her issues, but no one else. I figured that out just fine.
Just last week a client had the stupid Grammarly plugin wreck something online, fixed in minutes.
>Or they are behind a workplace firewall that blocks some specific ___domain used by the site.
Say, "Call your tech support guys, I am unable to fix that." I can't say that to a guy that is holding only a CD that got mailed to him, because I am the only support then.
>I've done support for a webapp, and I've had to use remote desktop sharing quite a few times.
Yep, and in the near future this will work in the browser, we are close now. And the beauty of the internet is that if they don't have access, we don't have to debug until they do. (their ISPs/intranet problem) But in the old days, it didn't matter what the issue was, and if the computer was not online, then the only data I could get to debug from was irate staff.