![]() Set persistent cookies => persistent.0 and persistent.1, next time will create persistent.0, persistent.1 and persistent.2. This problem occurs on the content process too late processed the removing cookie which from parent's notification.Ģ. Here's a video I recorded: Ĭhrome seems to be slower in processing cookies, but it works flawlessly: (on the last page refresh it takes a little bit more time to visualize the changes, but it does not affect the page - just a WebDeveloper toolbar lag). On some page refreshes either required chunks are missing, or already deleted chunks still exist in the cookies. The operation is performed abound 100 times. Before rewriting the data I always delete previous chunks. In the JS files I create small cookies (100 bytes each) that store one long string. I can confirm that the blazing-fast mechanism of cookies processing in Firefox Quantum is a result of operations going out of sync. ![]() ![]() Unfortunately my modifications made the chance of the error appearing a little bit lower than it was before, but I still see it. I have added the debug information you asked for in a separate file: !trash/ff-test-2.html
0 Comments
Leave a Reply. |