I've got a web app targeting .net 3.5 and im trying to render browser specific content, specifically targeting iPads. I've visited my page from various browsers including iPhone, iPad, Chrome, Safari and the Request.Browser variables always seem to be wrong. Apologies for the rant, I thought this was a .Net feature that worked out of the box.
This feature can be made to work by copying .browser files into your application App_Browsers folder. By default they live in %SystemRoot%\Microsoft.NET\Framework\version\CONFIG\Browsers.
Even still for some reason it was not detecting the different browsers that I was using, however I discovered the OceanAppleWebkit.browser by Owen Brady which worked immaculately for my purposes. It may be a bit dated by now but if you know of any updated sources for .browser files it would be appreciated if you post a comment with a link. Thanks!
http://owenbrady.net/browsercaps/
Related
We are using webspeech(https://www.drupal.org/project/webspeech) module for text-to-speech in one of our project. Basic functionality is working fine. But when we open this site in mobile devices (samsung, apple, sony) TTS feature is not working and no error is also being displayed.
We have tried to debug the problem but not able to do so.
Any help will be much appreciate.
If you read the module requirements it says specifically
Flash 9+ is required on client web browser. Modern browsers those
support HTML5 may also work but not guaranteed.
I see you opened an issue with the maintainer, which will probably be your best source of information, but it looks like you might be hit or (mostly) miss on mobile devices for now.
Hello Stackoverflow community.
Since the release of Windows 8 and thus, Internet Explorer 10, FCKEditor refuses to function with IE10. With the latest patches, Firefox 17 and Chrome work just fine with it.
I know FCKEditor is old, so I was thinking of moving to CKeditor but it seems, its implementation for classic asp webpages doesnt work with IE10 as well.
Any suggestions, on how to fix the problem, or any other editors (with the functionality of the above two editors) would be appreciated(classic asp only).
CKEditor should work with IE10.
Maybe there are some problems with it at the moment (I tested it briefly some time ago), but given that it's a supported version (opposed to the status of FCKeditor), if you file bugs reporting the problems they should be fixed eventually.
So recently Microsoft threw the joke that was IE6 into the recycling bin, and said that users should automatically be upgraded to the latest version of IE, if they hadn't already. Unfortunately for web designers, this means that some people (running XP) will be stuck with IE8.
I recently started redesigning a clients website to bring it up to date, and in order to make loading times quicker, save on disk usage, and on bandwidth, I have implemented the use of CSS3 code and then a big but... IE8 Doesn't support CSS3... :(
Is there a significant amount of users on XP / Vista / 7 who still use IE8, or have they moved to alternative, more up to date browsers such as Chrome, Firefox, Safari etc?
Should I worry about trying to find a way to keep the website looking correct in all browsers? or is there a way for me to encourage visitors using IE8, to swap it for another browser?
I imagine this depends on how the website is used. Is it an intranet website, a public website, or an web application that the owner dictates the version. IMO the best way to figure this out is to have Google Analytics plugged into the web app.
I can tell you that the project I am currently on doesnt have the luxuary to rule out IE8. 70% of our users that use the web app I work on use IE8. It seems to still be the most used browser in the business world. (at least from my experience) Heck we still need to support IE7.
However if you can guarantee the web users are using an up to date browser, then thats a different story. Or of course you can say, this app doesnt support IE 8 or lower.
Thats my 2 cents.
IE8 is the default browser in Windows 7, so expect it to hang around forever, just as IE6 has because it was the default in Windows XP.
Use http://code.google.com/p/html5shiv/ or http://code.google.com/p/ie7-js/ to ease the pain.
Yes, but according to WC3 the percentage of usage is now only ~8% for IE8.
Thats still a pretty big number to turn your back on however.
I am an asp.net developer looking to build a web app using iUI for the iPHone. I was wondering if this app would also display properly on other devices.
Thanks in advance.
Look at ASP.NET MVC. The routing engine can use different views to render the page depending on the agent provided by the browser. Hanselman has some great writes up on how this works:
MixMobileWebSitesWithASPNETMVCAndTheMobileBrowserDefinitionFile
TheWeeklySourceCode28IPhoneWithASPNETMVCEdition
iUI is based on HTML5 and CSS3. So yes, it will work on any device / desktop browser since it supports HTML5 and CSS3. Actually, only Webkit (Safari/Chrome/iPhone/Android) has a pretty good support of it, and Firefox 3.6 supports most of it too. Fennec 1.0 will.
Haven't heard if it was planned for IE9. Sure IE8 does not.
we are going to install IE8 in the company. We have many web based ASP.net applications.
I would like to evaluate the impact of installing IE8 on our asp.net applications. the applications are using .net 2.5 and 3.5. They use ajax in some cases.
I have never done such impact analysis so what is the best approach?
The approach is to run these applications in IE8 and see what happens.
After that you will write down what works and what breaks and attempt to estimate:
The time/work/money needed to fix what does not work
Costs and consequences of running for some time partially broken applications, until they get fixed
Advantages of running under IE8 (after everything will be fixed) vs. sitting with the good old IE7
That should give enough information to management to decide on how the migration will proceed.
I'd push out IE8 and change the IIS headers to force IE7 Compatibility mode by adding the following meta tag (the opening < and closing /> are removed so that the string could post):
meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7"
Make this change on all of of your ASP.NET sites. Then, as a site is updated to work in IE8, remove the header and IE8 will run in standards mode.
The first question I would ask is whether you have a compelling reason to move to IE8?
There are many websites that don't work (the whole reason that IE8 has a "compatibility mode"). The chances that you have done some of the same things these websites do to make them "incompatible" is fairly good.
There is no way around a need to thoroughly test your own applications before making the move.
We found that the move to IE8 actually broke some things in Visual Studio (seems it's a known issue) so didn't even get as far as starting to test the applications.
I am IE user and use Vista and develop in VS2008. IE7 became almost unusable and actually changed my default browser to Firefox. This caused more issues for me since I use msn hotmail and other things that seem to work together quite well (MS passport etc) I was also sceptical about upgrading to IE8, but did it. its better! I would suggest upgrading to IE8 and fixing what needs to be fixed anyway.