I am working on some website edits for a client and am running into an issue where the website no longer loads consistently in Safari. It will sometimes load if refreshed enough times but generally it just shows a white screen.
I have only made a couple of small changes to the site in their host Web.com's website builder (editing the navigation and removing a few buttons from pages), so I'm super confused on what would have caused this to happen. The website can be viewed here: https://www.larrypratt.com/
Has anyone encountered this sort of thing before? Thanks.
Related
I am having a strange issue that I think might be Chrome related but wanted to post here for thoughts.
I have some users who when trying to log into my node.js application, they press enter or the log in button and it just sits and spins and never times out or anything. When looking at the Network tab when this issue occurred the POST never showed up. I then put some alerts on the button click with javascript and as long as the button was in the tag nothing showed up.
Completely deleting the users' profile (suggestion from Google) made it work...until chrome updated and then it happened again.
Using any other browser, no issues. Chrome Beta, the issue shows up. Chrome Canary, I have had 2 users testing for over a week and they have not seen the issue reappear. Incognito has the issue occur as well.
Google Support asked me to send a HAR file to them. The interesting thing was when I opened up developer tools, went to the network tab and then cleared the screen to start a recording, the issue disappeared for that moment only.
It is working for 80% of my users so I can't see how it could be a coding issue, this is also a login that I created over a year ago and have not touched since.
If anyone has any insights I would love to know what might be causing this.
I've been playing around with GitHub pages for a while, and have been doing most of my development in Firefox. Everything was working amazingly, until I attempted to test my project page in Google Chrome. To my surprise, when visiting the same GitHub project page in Firefox and Chrome, Firefox was served the correct index.html page while Chrome was served a completely different (and incorrect) one.
I've poked around for a few hours now and honestly have no idea what's going on. Both Firefox and Chrome are requesting the exact same URL with an HTTP GET request and receive different responses from the server. I've tried changed the user agent and messing with the request header in both browsers, and it didn't seem to affect anything.
Does anybody have a clue what's going on? If it helps, the project page in question is "https://wgxli.github.io/complex-function-plotter/". Any help is much appreciated.
Edit: It appears to be related to a browser cache issue. The behavior disappears if I clear all data from the browser and visit the above page. However, if I clear the browsing data, visit the root directory of the above page, and then request the above page, the problem reproduces itself. At this point, I think I've reduced it to a question of why the browser (or CDN) is returning a cache hit when it shouldn't.
I ended up fixing the issue. I was using create-react-app, which automatically registers a service worker for local caching. I just disabled this service, which resolved the problem.
In my web site, 'sometimes' the font awesome icons are not loading. It shows only as squares.
When I googled I found out that to change the .htaccess file in the server. But my web site is hosted in weblogic server. Is there any equivalent to .htaccess file in weblogic.
I encountered this issue only in firefox. But other people have got it in IE 11 as well. In my case, when I clear the cache and open it, it loads also.
Pleade let me know, if anyone understands what's happening here. Thsnks in advance
I´m planning to make a full dynamic site using pjax, with static menu (only the content will be updated with pjax). How bad is this?
The site that i have planned to implat this on have a lots of data on it, most images.
I have tested my solution on my local machine and it seems to work but in production it will probably be slow or what do you guys think? Are this bad practise?
Now on pjax start i slide out my container to the left, and slide in the new content from the right. I have noticed a small performance lost when i do this in Safari and FireFox. Should i skip my solution and just do regular updates of the page? I want to do something like Twitters iPhone app, but on the web.
The reason i want to do this are that i have a full size google maps with a lot of pins that take some time to load.
I have found Tubrolinks (http://www.github.com/rails/turbolinks) that would be included in Rails 4.0, its great adn i think a good answer to my question.
I have had a report that my company's website is resizing at least one employee's browser windows. I experienced this behavior myself on the user's computer, and it was mystifying because the resizing only occurred on our site, not on any other site, and it occurred on both Firefox and Internet Explorer. The user has a Windows 7 machine running updated software. She has no add-ons, themes, or plugins besides the usual (Flash etc.) and her settings are the factory defaults. I cleared the browser cache on both browsers and restarted the computer and it still occurred. The only thing left is the css, but none of it seems suspicious to me.
What is happening is, when she clicks a button or internal link on the site, then when the new page finishes loading, the browser window resizes to approximately 80% of the width of the content. That is, the very last thing the page does as it loads is to resize itself. If she zooms in or out, then on the next load, it again resizes to 80% or so of the smaller or larger size of the content. If she maximizes and then loads a page, then the window resizes to 80% but somehow maintains the "maximized" icon. (You then have to click twice on the "maximized" icon to maximize.)
The reason I am flummoxed is that I thought this kind of behavior was something you could only do with JavaScript, but I deliberately tested this with pages that had no JavaScript at all and it still occurred. There is exactly one page on the website that has browser-resizing JavaScript on it, but it resizes to a pixel size, not a percentage, and it's part of a web service that wasn't in use while I was testing.
What kinds of things should I investigate to solve this issue? Because this is an employee, I have to either fix the website or fix her computer, so ideas for investigating both would be great.
The problem turned out to be that single page with browser-resizing JavaScript I mentioned. Another set of pages had needed some JavaScript functions from that web service, so one person had copy-and-pasted the functions that were needed. Then someone else came along, noticed that the copy-pasting was a dumb idea, and decided to simply include the JavaScript file that had those functions instead.
The problem was, the command to resize the window was bare in that file. For that one user, that command was being carried out and resizing every window. For everyone else, their browsers were ignoring the resize command except on the web-service popup window. I can only assume she had the problem because she had factory-standard settings, and the rest of us didn't. To fix the problem, I moved the resize command from the JavaScript file to the head of the web service page.