We are working on a Java EE project for some time now and recently we have experienced a problem where suddenly on some clients the pages wouldn't load.
Using firebug we saw that some Javascript resources didn't load (the attached pic) and then by testing via Wireshark we found out that Firefox doesn't send a request for these resources.
The interesting part is that after deleting the local Firefox cache on a client that page loads as normal, therefore it seems there is a problem with resources that are cached locally.
As we have never experienced this until recently could it be due to a bug in newer versions of Firefox (28+) as we have never experienced this on something like Chrome? Any help would be much appreciated
Related
I recently received a report from a Mac/iPad user who used my Blazor server-side application. The problem seems to be that when they put the Safari browser in the background (e.g. switching to another application like Twitter to talk with me), the application disconnects:
This does not occur with any device/browser combination that I have tried with Windows (my native/development environment).
I am in the process of acquiring an iPad to test this on in my local environment, but I am wondering if anyone out there has had any experience with this and/or if there is a remedy to it.
Any assistance/pointers would be appreciated.
According to this Reddit thread, this appears to be due to a known issue:
https://www.reddit.com/r/Blazor/comments/x78buq/blazor_serverside_safarimacipad_connection_issue/
It is captured here in this issue with Github:
https://github.com/dotnet/aspnetcore/issues/30344
I found this plugin, for Firefox, on Google and it looks like perfect to test if my site works well on all major browsers. It changes the browser's user-agent and emulates almost all versions of all browsers on any OS, including mobile. Looks like perfect. My question is: can i trust 100% on this plugin? It really give me the same effect as if i were using other browser (ie6 for exemple)?
It really give me the same effect as if i were using other browser (ie6 for exemple)?
No. Changing the user-agent string does not mean you are changing the browser's rendering engine - it just sends a different browser signature to the server. The actual rendering will always be Firefox's, at the sites will always look as they do in Firefox.
See these questions on how to test sites in different browsers:
Browser testing - Ideas on how to tackle it efficiently
https://stackoverflow.com/questions/464089/simulators-emulators-for-mobile-browser-testing
It does not affect the rendering engine of your browser. It only pretends to the server to be a different browser, so if the server has e.g. a special IE6-optimized version it will send you this version instead.
Essentially, this is mostly useful to access web pages that claim to not support your browser by pretending that you have a supported version.
For testing cross-browser compatibility it is useless.
You can get free screenshots from a wide array of browsers at http://browsershots.org/
that is a very useful site, but won't help you test JavaScript interactions.
I have been using prototype's Ajax.Request for making ajax calls.
With the new versions of google chrome browser,this call seems to be breaking.
The onLoading function of Ajax.Request seems to be triggering
after onSuccess and also the overall request processing is not happening as expected.
This happened to be from the version 14.0.835.163 of the chrome browser.
Prior to this version, it was working normally.
Has anybody experienced such an issue.
Chrome's fast iteration of versions makes it prone to releasing bugs more often that other browsers. I would suggest writing up a test page and submitting a bug to them here before it makes it to production:
http://code.google.com/p/chromium/issues/entry
There is also a newer version out as we speak: 14.0.835.202 (Official Build 103287) Try updating to that version and see if the problem persists. Lastly, try switching to the beta channel and see if the problem persists there.
http://www.google.com/landing/chrome/beta/
I'm developing a web app and during the tests I noticed that sometimes browsers don't load all images (like background or some decorative images) on the website. I need to hit the refresh button to to have it fully loaded. This usually happens when the website is visited for the first time.
I suspect that maybe the development server is not fast enough and browsers "assume" that the links to images are broken because there is no fast response from the server. But I'm not sure. At the moment my development server is on a remote host inside VirtualBox with Ubuntu-server 8.04. I know that it is not the best configuration, but I'm not sure whether this is indeed the case. Or maybe it is due to some apache/php configuration parameters?
I would appreciate any suggestions or clues.
Many thanks
Please take a look at this code:
http://3wcloud-com-provisioning-qa.appspot.com/testAjaxDojo
Just tab off the "domain" input field to try to make the Ajax run.
(Note: the test Ajax web service always sends back the same message, it pretends to check if domain is available but it really doesn't).
When running in Firefox 3.5, I get "dojo not defined" on the dojo.xhrGet statement.
It works fine in IE7 and Chrome browsers, and one friend tested on Firefox 3.0 and it worked.
1) Is there something wrong with Firefox 3.5 not properly getting the dojo javascript from the CDN? Possibly a caching issue?
2) Do you Dojo gurus know of this problem? Is it something that has already been reported to Firefox?
Thanks,
Neal Walters
Update: 9/1/ afternoon - I have uninstalled and re-installed Firefox 3.5.2 (but I kept my profile settings), and got same problem. I'm on Windows Vista Ultimate.
Finally found the problem. It was the add-on called "No-Script". Even though I had set No-Script to allow scripts globally, something in that tool was causing the issue. I upgraded to new version of No-Script and still had problem. If I disable the add-on (from the Tools/Add-ons screen), then Dojo loads perfectly from the CDN and life is good again.
I probably lost 6-8 hours on this stupid issue. Hope this posts saves someone else the time. Please "vote-up" the answer if it does.
As I stated in my comment, on Firefox 3.5 (mac) works fine. Try to do the following on your Firefox browser, insert the dojo library url in the url bar:
http://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo/dojo.xd.js
Usually it helps to solve any cache problems and forces Firefox to fetch the file.
If it still doesn't work, just store dojo in your server and use it locally.
It's working fine here with NoScript enabled.
I just needed to allow both "3wcloud-com-provisioning-qa.appspot.com" and "ajax.googleapis.com".