Though I have not yet checked your code, from the comment I can say that the browser works as expected.
Browser will have two clients (authenticator and an unregistered client) and when you load the page twice I assume that there are 2 more clients which takes the count to a total of 4 clients. No more clients can connect from the IP. When you restart the browser, the clients get destroyed and starts fresh.
The work around will be to free the client object on page unload. I will also check your webpage code to confirm
I just joined the rate limited test (with the latest binaries) and browser and whm both worked perfectly and the auth UX looks excellent - one question on this: what is the point of the Skip link (top right). It appears redundant and could be removed.
I have uploaded a slightly updated safe://rsports page. Can you name the bird (find it first )?
The changes made to the email app are not backward compatible that’s why it doesn’t load your previous email IDs. I was thinking of making it backward compatible but I considered it a waste of effort at this stage.
I hope that a longer time between internal / restricted community testing and public testing translates to a shorter time between public and the test being designated as Alpha 2 (and the beginning of the next sprint to Alpha 3). It’ll be great if most significant bugs are already squashed by the time the public test arrives, and it sails through.
I am not experiencing any such issues, I deleted my index replaced it with an updated version along with an added file. Updated fine for me. (its-coming)
I tried again, deleting the www-root for safe:polpolrene and uploaded it again and it works. I then removed all data in that map and the browser gave an error but didn’t crash. So looks like things are magically fixed some way or the other.
safe://polpolrene and safe://davidspeaks are both online again.
)?
