| 2006-10-24 04:50:42 |
Matthew Paul Thomas |
rosetta: statusexplanation |
Hi Matthew,
I couldn't reproduce this here.
Is this reproducible in launchpad.dev?
Thanks |
I just reproduced it on production. I can't reproduce it on launchpad.dev because it's local and not over HTTPS, so it's too quick. Updated description coming. |
|
| 2006-10-24 04:59:25 |
Matthew Paul Thomas |
description |
If, while logged out, I visit <https://launchpad.net/products/schooltool/2006/+pots/schooltool/lt/170/+translate>, the resulting login page has *two* consecutive banners saying "To continue, you must log in to Launchpad". There should be only one. |
1. Become logged out from Launchpad, for whatever reason (e.g. because you cleared your cookies).
2. In one window, open a page that requires login (such as <https://launchpad.net/products/schooltool/2006/+pots/schooltool/lt/170/+translate>).
3. Before the first page starts loading, in another window, open another page that requires login (such as <https://launchpad.net/products/launchpad/+filebug>).
What happens: One of the resulting login pages has two consecutive banners saying "To continue, you need to log in". On the other page, this text isn't present at all.
What should happen: The text should appear once and only once on every login page.
This is a side-effect of the way we handle alert messages, because we don't cruft up our URLs with tokens linking a particular message to a particular browsing path. However, we know that the login page should *always* contain the text "To continue, you need to log in", so it needn't be implemented as an alert message in the first place. |
|
