Bug 1898899 Comment 14 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Andrew Overholt [:overholt] from comment #12)
> Maybe we should consider an intervention?

I'd previously suggesting holding off on that because there was a site redesign that was supposedly days-or-weeks away from deploying, which meant that the site content might radically change as soon as we deployed it.  An [archive.org snapshot from August 2024](https://web.archive.org/web/20240821053846/https://www.pge.com/en/featured/new-pge-account.html ) shows "This fall, we’re launching a new online account [...]"

However, that timeline has apparently been pushed back by ~half a year to "Spring 2025" based on https://www.pge.com/en/featured/new-pge-account.html which now says "a new pge.com account is coming in Spring 2025"

So, in light of that, yes, it's probably worth deploying an intervention here, if/when we can come up with one.  I don' t have one to suggest yet but +CC :twisniewski who may be able to help with discovering and/or shipping an effective intervention here.

Note, that page also has one other clue there about why they might be aggressively showing a banner about Firefox/Brave being unsupported:
> ...you will only be asked to use MFA [...] If too much time passes between logins
> 
> If you're using a browser with extra security controls like Firefox or Brave, you may need to use MFA every time you log in. Some browsers prevent us from saving your information.

So it's possible they're hitting some 3rd-party-cookie or tracking-protection issue that prevents them from saving the cookie that they use to recognize you as a previously-authenticated user.
(In reply to Andrew Overholt [:overholt] from comment #12)
> Maybe we should consider an intervention?

I'd previously suggesting holding off on that because there was a site redesign that was supposedly days-or-weeks away from deploying, which meant that the site content might radically change as soon as we deployed our intervention.  An [archive.org snapshot from August 2024](https://web.archive.org/web/20240821053846/https://www.pge.com/en/featured/new-pge-account.html) shows "This fall, we’re launching a new online account [...]"

However, that timeline has apparently been pushed back by ~half a year to "Spring 2025" based on https://www.pge.com/en/featured/new-pge-account.html which now says "a new pge.com account is coming in Spring 2025"

So, in light of that, yes, it's probably worth deploying an intervention here, if/when we can come up with one.  I don' t have one to suggest yet but +CC :twisniewski who may be able to help with discovering and/or shipping an effective intervention here.

Note, that page also has one other clue there about why they might be aggressively showing a banner about Firefox/Brave being unsupported:
> ...you will only be asked to use MFA [...] If too much time passes between logins
> 
> If you're using a browser with extra security controls like Firefox or Brave, you may need to use MFA every time you log in. Some browsers prevent us from saving your information.

So it's possible they're hitting some 3rd-party-cookie or tracking-protection issue that prevents them from saving the cookie that they use to recognize you as a previously-authenticated user.
(In reply to Andrew Overholt [:overholt] from comment #12)
> Maybe we should consider an intervention?

I'd previously suggesting holding off on that because there was a site redesign that was supposedly days-or-weeks away from deploying, which meant that the site content might radically change as soon as we deployed our intervention.  An [archive.org snapshot from August 2024](https://web.archive.org/web/20240821053846/https://www.pge.com/en/featured/new-pge-account.html) shows "This fall, we’re launching a new online account [...]"

However, that timeline has apparently been pushed back by ~half a year to "Spring 2025" based on https://www.pge.com/en/featured/new-pge-account.html which now says "a new pge.com account is coming in Spring 2025"

So, in light of that, yes, it's probably worth deploying an intervention here, if/when we can come up with one.  I don' t have one to suggest yet but +CC :twisniewski who may be able to help with discovering and/or shipping an effective intervention here.

Note, that new-pge-account page also has one other clue there about why they might be aggressively showing a banner about Firefox/Brave being unsupported:
> ...you will only be asked to use MFA [...] If too much time passes between logins
> 
> If you're using a browser with extra security controls like Firefox or Brave, you may need to use MFA every time you log in. Some browsers prevent us from saving your information.

So it's possible they're hitting some 3rd-party-cookie or tracking-protection issue that prevents them from saving the cookie that they use to recognize you as a previously-authenticated user.

Back to Bug 1898899 Comment 14