Problem detail: I've been troubled with this issue for a week til now. I've also posted on github but no one answered. https://github.com/vercel/next.js/issues/45937
This is a bug with getStaticProps with fallback: true onSafari + MacOS Ventura or Safari+ iOS 16.3
It works fine in Chrome:
Prefetch URLs return 200 once then next time they always return 304:
On Safari:
Prefetch URLs always return header 200. And the caching doesn't work, it still needs to fetch again when I click the link.
I'm glad to give away a beefsteak meal to someone who can solve this issue.
I've tested on localhost on safari and it resulted the problem same as always. no cache returned.
Expected Behavior
Safari should work the same as Chrome. First time http status should be 200, the 2nd time is 304.
Related
First off I apologize if there has already been a similar question before, I honestly couldn't find any.
I'm currently developing a chat using Firebase and thanks to the decent docs I'm making good progress so far, so this isn't really the issue here. However, while testing I stumbled across a little issue that might possibly be a bug.
For managing presence in my chat, I am pushing values to a location that corresponds to my user's unique ID. This pushed value is then removed on disconnect.
By doing it this way, I can reliably determine a user's status without worrying about his number of concurrent connections to my Firebase (i.e. browser tabs).
This is actually working fine with Firefox, Chrome and Safari, but there seems to be an issue with Opera. When using Opera, if you close the tab in which the chat is running, the value that should be removed on disconnect is not. It will be removed eventually after like 2 minutes or so, but it is taking way too long, considering that the same thing is happening instantaneously when using another browser.
Out of curiosity I've tried the presence example using Opera and I was able to reproduce the exact same behavior. If I open the corresponding Firebase in another tab, then run the example, enter a name and finally close the tab that the example is running in, I can see that the value in the corresponding Firebase is not removed as I close the tab.
I would appreciate if you could tell me if this is just me doing something wrong or if it is actually a bug.
Regards
Muddy
Opera has a different model for page transitions than all other browsers. Most browsers fire events when loading and leaving a page. Opera actually keeps old pages hot in memory in order to make the back button faster. When you click "back" in opera it's actually resuming the old page.
As a result, there's no way for us to know exactly when someone has left a page in Opera. As a result, we're forced to simply wait for a server timeout to determine someone has left.
So, short answer, onDisconnect operations DO work in Opera, but they might take a couple of minutes to take affect. In all other browsers the operations will happen immediately if the connection was terminated cleanly, and after a few minutes if it was not.
Does anyone already found the solution for the problem that chrome has after the latest update. When you post something to the server it takes chrome more then 20 seconds to load.
We checked the same site in IE and FireFox everything loads pretty quick.
Its seems to be a bug in the new update.
I've googled this and can't seem to find anything. I inherited a Frankenstein website recently that needed some changes. The site displays fine in all Firefox, Chrome and IE7 and IE8 (in Windows XP).
However, In IE9 (Windows 7), I randomly get a blank IE 404 page (not the 404 page not found file that you'd get normally) though in some cases it replaces the content with a 404 error.
Here's the site : I didn't build it so please don't judge me on the use of tables and non-standards compliant HTML and CSS. Unfortunately the client is strapped and is not paying for a re-design.
One Accord Trucking Jobs
The site is a mashup of Jamit software and WordPress.
I'm really not sure why this is happening. I can't find anything on google about IE9 doing this.
Well, for what it's worth, adding
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
to the header files and fixing some of the horrendous markup did the trick, as near as I can tell.
There are frames, iframes and pretty crappy standards in their coding, both on the front end and on the back end. They were using loose as a doctype! Also there were some weird conflicts with character encoding.
It was also pretty random, and one particular fix didn't help 100%, the 404 messages just happened less frequently. I've refreshed several of the offending pages 50+ times each with not a single incidence so I'm going to say it is now fixed.
I hope my fix helps somebody else at some point.
Edit: Well, I don't know how to set this as resolved. I guess I can't set my own answer to resolved, so perhaps somebody can post and I'll set yours as the answer? Thanks!
Since you have WordPress integrated with external code, this sounds like a situation where wp-blog-header.php in WordPress may gratuitously set a 404 status header. A workaround to this is to manually reset the status header to 200 after requiring wp-blog-header.php:
require_once('../wp-blog-header.php');
status_header('200');
Another workaround is for users to uncheck the Advanced setting in Internet Options called "Show friendly HTTP error messages". If that is unchecked, then IE will behave like other browsers, which appear to ignore a 404 code in cases where content is returned from the request.
I'm using the Selenium 2.0 web drivers to try and login to a page. The following code works with the Firefox webdriver just fine, it finds the fields, fills them in and clicks the button.
driver.FindElement(By.Id("UserName")).SendKeys("name");
driver.FindElement(By.Id("Password")).SendKeys("test");
driver.FindElement(By.Id("btnLogin")).Click();
However, whenever I try to use the internet explorer webdriver it says it is unable to find the element with id == UserName. I tried using By.Name, and By.Xpath as well with valid inputs but I still get the same error saying it can't find the element. I am using IE 9 so I'm aware it may be a compatibility issue, however I can't seem to find any posts or information saying there is a known issue.
I just wanted to see if anyone else was experiencing the same issue, or if there is something I'm not doing correctly that is causing my issue. Also, this is a C# .NET project.
-- Edit --
Apparently it is an issue with IE9, I removed 9 and went back to 8 and the test works. I'm still interested to know if anyone finds out why this happens or if there is a work around.
The current release of Selenium (2.0b2) does not support IE9, however 2.0b3 should be released soon and supports both IE9 and Firefox 4.
This answer may also be relevant for anyone experiencing issues getting 'clicks' to fire with IE9.
A workaround to this is to send a .Click() to another element on the page, so that the browser gets the focus, before attempting to click the link, e.g. it's parent:
driver.FindElement(By.Id("Logout")).FindElement(By.XPath("..")).Click();
driver.FindElement(By.Id("Logout")).Click();
I was wondering if anyone can help me out. I've got a page that shows about 260 images so it obviously takes a long time to load. I've noticed a lot of the time in Chrome it takes too long to load, and by too long I mean it appears to be unresponsive.
Safari on the other hand seems to load the page up pretty quickly.
So I am left here wondering is there something that exists in the lifecycle of a chrome http request that would be trying to pre-load the images or something to that effect which is causing the delay.
Both browsers are working from an empty cache.
Can anyone enlighten me!
The network tab on the chrome developer tools will let you see the order the images are loading in, and the average time fetching each from the server. I've seen issues where a certain higher res image can cause a browser to stutter a bit when rendering the page (usually IE :s), so this might help you pinpoint if its a particular image causing the issue.
http://code.google.com/chrome/devtools/docs/overview.html