| From looking at the code that is in the current browser.js file we attempt to
do at least 2 things: 1. identify the browser 2. identify the platform Here are the problems that I see. We only support MSIE or NS, so why do allow for browsers that spoof, such as Opera, to get by? Why not explicity detect them so that we can alert that they are not supported? When we attempt to detect the platform we are using methods that are almost guaranteed to fail. I'm not saying that the entire thing should be included, but at the least shouldn't we fix the most obvious problems which have an effect on the way in which the DynAPI works? BTW, since I can't seem to find a list of the CURRENT GOALS, can someone post them to the list for me. I would like to learn more about them and see what can be done to meet them before the future becomes the past and we get stuck in the present. |
- [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Browser.js R... anders . noras
- RE: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Bro... Eytan Heidingsfeld
- RE: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ]... Cameron Hart
- [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Browser... JonathanErinDale
- Re: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Bro... Doug Melvin
- Re: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ]... Steve Carroll
- Re: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Bro... JonathanErinDale
- Re: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ]... Doug Melvin
- Re: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ]... Richard Bennett
- RE: [Dynapi-Dev] Re: [ dynapi-Patches-407882 ] Bro... Scott, Leland
