webcompat / web-bugs

A place to report bugs on websites.
https://webcompat.com
Mozilla Public License 2.0
742 stars 65 forks source link

www.medicare.gov - site is not usable #139476

Closed theloniusgh closed 2 months ago

theloniusgh commented 2 months ago

URL: https://www.medicare.gov/account/login

Browser / Version: Firefox 128.0 Operating System: Windows 10 Tested Another Browser: Yes Chrome

Problem type: Site is not usable Description: Page not loading correctly Steps to Reproduce: after logging into medicare.gov I went to view a page showing my recent charges. Firefox would not load the page. Chrome would. See screenshot. this is a recent change, Firefox loaded the page before.

View the screenshot Screenshot
Browser Configuration
  • None

From webcompat.com with ❤️

theloniusgh commented 2 months ago
View the screenshotScreenshot
sv-calin commented 2 months ago

We appreciate your report. Unfortunately, a special account is needed in order to sign-in. (account creation requires valid data)

image

If the reporter (or anyone else) can do a more in depth test and provide more information (console logs/errors/screenshots) regarding this issue, feel free to reopen and leave a comment (or you can send us an email with the test account credentials and we will test it on our own).

Suggestions: • Clear cache/data/cookies, disable Ad-blocker (if available), or use a clean profile and check again • If there are any changes made to the default settings of the browser (e.g. in about:config), please revert to the default settings

How to create a new profile:

  1. Open a new tab
  2. Type in the address bar "about:profiles"
  3. Press "Enter"
  4. Click on "Create a New Profile"
  5. Click "Next"
  6. Name your profile
  7. Click "Finish"
  8. Head to your newly created profile
  9. Click "Launch profile in new browser"

Note: You can return to your old profile at any given time by accessing "about:profiles" in the address bar

[qa_30/2024]

sv-calin commented 2 months ago

Closing this as incomplete since we are not able to test this issue due to a lack of valid credentials. Feel free to reopen and leave a comment if you have any updates regarding this issue.

[inv_32/2024]