The password reset window now dims the whole page
If you opened "Forgot password?" on the log in page, the reset window appeared, but the dark backdrop behind it only covered a narrow strip the width of the log in card. The rest of the page stayed bright, so it looked like two layers fighting over the screen and it was hard to tell what you could still click. The cause was a small layout detail: the log in card slides up into place when the page loads, and the leftover position from that animation quietly shrank the area the backdrop was allowed to fill. The reset window now opens on top of the whole page instead of inside the card, so the backdrop dims everything edge to edge, on a phone and on a wide monitor alike. Nothing else about the flow changed. You still type your email, press Send reset link, and we email you a link to choose a new password. Clicking anywhere on the dimmed area or pressing Back to log in closes the window and takes you back to the form exactly as you left it, with whatever you had typed still there. This is a visual fix only. Your account, your password and the way reset emails are sent are untouched, and there is nothing you need to do on your side. If the page still looks off after this update, a hard refresh will pick up the new version.
624 words
The "Forgot password?" window now dims the full page, not just a strip behind the log in card.
Clicking the dimmed area or Back to log in still closes the window and keeps what you typed.
Nothing changes about how reset emails are sent or what your account looks like.
Portail v2.6.16 shipped on 2026-10-10 as a patch release focused on the password reset window now dims the whole page. If you opened "Forgot password?" on the log in page, the reset window appeared, but the dark backdrop behind it only covered a narrow strip the width of the log in card. The rest of the page stayed bright, so it looked like two layers fighting over the screen and it was hard to tell what you could still click. The cause was a small layout detail: the log in card slides up into place when the page loads, and the leftover position from that animation quietly shrank the area the backdrop was allowed to fill. The reset window now opens on top of the whole page instead of inside the card, so the backdrop dims everything edge to edge, on a phone and on a wide monitor alike. Nothing else about the flow changed. You still type your email, press Send reset link, and we email you a link to choose a new password. Clicking anywhere on the dimmed area or pressing Back to log in closes the window and takes you back to the form exactly as you left it, with whatever you had typed still there. This is a visual fix only. Your account, your password and the way reset emails are sent are untouched, and there is nothing you need to do on your side. If the page still looks off after this update, a hard refresh will pick up the new version. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.
The main changes were direct: the "forgot password?" window now dims the full page, not just a strip behind the log in card, clicking the dimmed area or back to log in still closes the window and keeps what you typed, and nothing changes about how reset emails are sent or what your account looks like. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.
This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.6.16 moved that contract forward in its own narrow lane.
The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.
The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.