In my device, S60 5th edition
OS: Symbian S60 5th Edition Browser: 7.1
Useragent: Mozilla/5.0 (SymbianOS/9.4; Series60/5.0 NokiaN97-1/12.0.024; Profile/MIDP-2.1 Configuration/CLDC-1.1; en-us) AppleWebKit/525 (KHTML, like Gecko) BrowserNG/7.1.12344
There is no issue with cookies, cookies are working normally. But Link Button control do not works. Actually, as I think, ASP.NET server does not send javascript code to perform a post back. That's why It says '_doPostBack()' not found.
It got fixed if I change target framework version from 4.0 to 3.5.
What is the easiest solution for this problem..??
The reason some that some controls do not work on Symbian browser is that .Net injects a javascript function called __dopostback() into the page.
The controls call this function to cause a postback.
Symbian has a problem with the double underscore and cannot find the function.
Although I do not know how to fix it, I do have a workaround;
My default.aspx page has a javascript function called __Redirect() which redirects to the normal page that uses link buttons etc. If a device that does not recognize the double underscore, they are not redirected and stay on this "basic" page. on this page, I use hyperlinks etc.
I think you should check if the same link button is not working on all sites? I think its a site specific issue considering the fact that .NET version change makes the button work. As for the "easiest" solution, its certainly not on the device.
Related
I made a lot of research on this topic but none of the found solutions helped me.
So, let's start: I have a VB ASP.NET WEB Application.
The problem is the users can see the source code of the aspx files in the browser (IE) when the Display intranet sites in Compatibility View is unchecked.
I tried all of the methods, settings compatibility from IIS, web.config or even from the meta tags from <head>.
I discovered that also with the checkbox unchecked if I use Enterprise Mode the browser displays the page ok.
I tried then to find a solution to force the Enterprise Mode from code but I didn't find anything without changing registry keys. Changing registry keys can also be done to the above checkbox.
If I go in the DOM Explorere in IE and I try editing the source, anything I delete from there, the page is displayed ok.
How can I force the Enterprise Mode, or the Compatility View Mode from code? or is there another solution for me to solve this problem?
In my opinion you need to check the caching of the application if you say that if you modify something in DOM the page appears.
I created a new VS 2013 project and viewed the default.aspx page with the Firefox browser. When I check the net calls it has made, I see it making constant calls to:
http://localhost:50682/6a663a78019845d5ade4a328cad09cc2/arterySignalR/poll?transport=longPolling&connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAOBmDwPWa2ky2MAZXFHBMVAAAAAACAAAAAAAQZgAAAAEAACAAAADSADQXBVKiKczflJ0OzUjOLduFTJE4zd%2FLHWGpDfXnuAAAAAAOgAAAAAIAACAAAACyEX81VwilygfphPoEKCYQ6ZwrkzExoKfZzEMkqBKqqzAAAADG%2BDJbrEFOfsNm9OKhqacnGseQvrwy5kmyZnI5YJiZbjYFgzMELXHfwA7Sxjj4osJAAAAAvQvoG4N0nn8eB9FRaJaZyqaUDF%2F9ypvGN%2B%2BVefnx8U1Fq6P9HXO9vEC%2BfA2s8R4jik58rD4IcFMjM4P8l5kv6g%3D%3D&messageId=d-F1180A0E-W%2C0%7Cl%2C4%7Cm%2C0&requestUrl=http%3A%2F%2Flocalhost%3A50656%2Fdefaulttest&browserName=Firefox&tid=4&_=1384207744328
Why is it doing that?
How do I stop those calls?
I see an infinite number of calls made to the above URL every 6 seconds.
Please help me understand this and fix this.
This is working as intended. Artery aka BrowserLink is a real-time connection from Visual Studio to all browsers running your code. It essentially allows Visual Studio to interact with every browser.
For instance if you have IE, Opera, Chrome and Firefox all running your code and you're trying to ensure cross browser correctness; instead of going to each browser and hitting f5 to refresh you can just click the browser link refresh button which will auto-refresh all of the pages for you.
Not everyone wants or needs to have this functionality so if you do want to disable it, as Gustavo Armenta said you can disable it by following the steps here: How can I disable __vwd/js/artery in VS.NET 2013?
I would recommend you to read this post first Browser Link feature in Visual Studio Preview 2013 to understand about this new feature that comes in with VS 2013.
And then to disable this, simply uncheck the "Enable browser link" option.
You can hide the polling requests from the Chrome developer tools Network tab so that the requests you are actually interested in become visible. You can hide the polling requests by adding a negative filter:
On the Network tab, click the filter button to open the filter options
Enter "-poll" without the quotes to hide the polling requests.
Example:
Had issues with that on site running with KnockoutJS framework. Pages were freezing for 10 seconds until "BrowserLink" external scripts were loading (using Chrome browser).
Issue solved by disabling "Browser link" feature in VS 2013
Steps How to disable "Browser link" (thanks to Gustavo Armenta for leaving comment with link in question)
I'm having a strange issue:
I can't login at http://maskatel.info/login, when I try to click the login button (the blue button that says Connexion), nothing happens at all.
So I opened up the developer tools in Chrome (f12) and saw the following JavaScript error every time I click the button: Uncaught ReferenceError: WebForm_PostBackOptions
I then found out that this function should be in WebResource.axd, I then went to the Resources tab in the developers tool and found out that this 'file' is not there and it is not loaded in the HTML source.
I tried a lot of different things without any success and finally tried another browser and it works fine in any other browsers. That same page was working perfectly previously in Chrome on the same computer in the past.
So then I tried to click the small gear in the Chrome developer tools and went to the overrides section and changed the UserAgent to something else and refreshed the page and it works perfectly with any other UserAgent string. The correct UserAgent when not overridden for my browser is Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.57 Safari/537.36
So right now I really don't know what to do next:
Is this issue related to the latest version of Chrome? I have not found any information on release dates for chrome.
It could also be a DotNetNuke problem but I doubt it since nothing there changed before and after the problem
It could also be asp.net related (I renamed App_Browsers to App_Browsers2 and still no luck.
Any help would be appreciated.
A data file which addresses this issue is available to download from the following url.
http://51degrees.mobi/portals/0/downloads/51Degrees.mobi-Premium-20130823.dat
.NET users will need to perform the following steps.
Download the above data file.
Replace the file 51Degrees.mobi-Premium.dat in the App_Data folder of the web site with the data file downloaded, renaming the downloaded data file to 51Degrees.mobi-Premium.dat
Restart the application pool servicing the web site to apply the new data file.
Some configurations may place the 51Degrees.mobi-Premium.dat file in a location other than App_Data. The web sites current location can be found in the 51Degrees.mobi.config file found in either the web site’s root folder or the App_Data folder. See the following page for more details.
https://51degrees.mobi/Support/Documentation/NET/WebApplications/Config/Detection.aspx
Please use contact us if you have any issues deploying this data file.
We are having this problem on all our DNN6 sites at work (we can't update to DNN7 since we are stuck on SQL Server 2005 and Windows 2003 boxes). DNN support ticket response was:
"This is a known issue with the Google Chrome update to version 29, the browser is having many issues with ASP.Net pages. The current workaround is to use a different web browser until Google can release a new update."
but I know big asp.net sites like redbox and msdn.microsoft.com are working fine, so it's definitely not a global problem.
Our servers are patched by our infrastructure folks, and they are usually up to date (patched regularly), so not sure what specifically is the issue.
I have personal sites on DNN6 (3essentials hosting), that are working fine. So its definitely not all DNN6/7 sites that are having problems. Maybe its DNN6 sites that are running on Windows 2003 boxes?????
It looks like someone has found the culprit at google. It is related to 51degrees that reports a version 0 for Chrome 29 user-agent string.
More details at https://code.google.com/p/chromium/issues/detail?id=277303
I tried to update the premium data (it is a professional edition installation) but I only get the same version that was aready there dating from 2013-08-15 and having 109 properties.
Then I tried renaming the App_Data/51Degrees.mobi-Premium.dat to add a .old at then end, but the system redownloads that file (same one looks like) to that directory.
So I went away and commented out the fiftyone configuration in the web.config file which instantly made the site work again for Chrome 29.
Let's hope there could be an update on a beter solution for this, but I think the culprit is finally found at least.
On a DNN 7.1.0 site, that uses the Popup feature in DNN (login window opens in a modal popup) the login functionality appears to work fine.
I would recommend you try the Popup option, and if that doesn't work, look at upgrading to the latest release of DNN.
update: I tested the same 7.1.0 site using /login instead of the login popup and it also still works fine, so I would encourage you to look at upgrading your DNN instance.
Is there a way to get MonoDevelop to not open a Safari (or other browser) window when I debug a web site? I still want it to fire up the XSP web server, and kick into debugging mode.
Reason being because I'm hitting the server code being debugged from another location, and I don't want to have to keep closing useless browser windows over and over.
A bit of a hack, but I'm now just calling window.close immediately after the page loads from JavaScript.
I'm on Linux, and I'm not sure if it will work for Mac, but this is the only relevant thing I found by searching for the same problem on Linux, so this answer is relevant to someone.
I go to the choice of browser (in the build options near the build button) and choose to open it in Vim. For some reason it doesn't want to open in Vim, even though it opens in LibreOffice and in Atom editor just fine. Ergo, it doesn't open anything. So A) this allows page refreshes on the home page. B) There's no opening and closing. C) You don't change any code to modify functionality of an editor.
I have created a simple app with a page having a server side form, three fields and a button that submits and performs two operations - 1) adds the form fields to the database table 2) sends an email. Now everything works fine on the web browser on my machine but when I access the app through my mobile, the page does not seem to work. the UI and all are set but the button click functionality doesnt seem to be working and also the label which is set after a successful submit is already visible and showing the "thank you" message. Am i doing something wrong here?
I have checked the app on Nokia Smartphone browser, android phone, and iphone simulator.
1st i would try to access the site from a different computer or through a proxy. Just to make sure things work out well in different browsers. That may catch your bug. It may be working fine on your PC Locally, on a local web server, but may not be uploaded to the web.
Next, I would check to see if the devices you are using support Javascript. Chances are good that your script relies on it.
I strongly recommend you to use JQuery Mobile, it create Mobile friendly interface for your website. and for sure it work the same for each cell phone, but as Asp.net isnot easy to render for most of (old) phones, so that you're not able to use whatever you like.