![]() But this is a fact of life in any organization and especially smaller (size and thinking) ones where there are big egos and weak leadership. It shows what happens when enough planning isn't put into a process and what happens when one group is allowed to make decisions in a vacuum without talking to other groups about potential issues. Also, PeopleSoft does not support browsers besides IE so PS users are forced to use IE while everyone else can get locked out of other apps when they hit the IE cookie limit. Because we have so much in our domain we hit a wall with IE. We do it because IE has a problem with how many cookies (and how large cookie storage can be) per domain. So as far as I'm concerned, I'm glad these security measures are there, because this is an extraordinarily bad idea in the first place, even without the security risks. Sorry, I know this ain't the place for arguing, but I do believe this needs to be clear because it's a real problem in web development that really does waste time and really does cost money and really does harm the web as a whole. Warn them if your site is designed specifically for a particular browser, that's fine, but don't make the actual decision for them. It's immoral to make those sorts of decisions for your users, no matter how dumb they are. ![]() ![]() I think I can safely speak for the overwhelming majority of experienced web developers, that techniques designed to dictate to the user which browser to use are always, always, always wrong, not just technically but morally. What you're trying to do should be absolutely unacceptable in no uncertain terms to every single user and developer. I'm sorry, I just have to nitpick a bit here. ![]() ![]() The real reason is security, which will (hopefully) always prevent you from running applications on the user's computer, but even if there weren't for that reason. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |