1654421 - Some CSS buttons on the site https://uplink.in.gov are broken since a recent patch on Firefox 80 Nightly build.

Status: UNCONFIRMED

(Core :: DOM: Navigation, defect, P5)

Description

[ice2jafar]

Attachment: Screenshot_2020-07-21 unknown png (PNG Image, 1920 × 1030 pixels) - Scaled (66%).png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0

Steps to reproduce:

https://uplink.in.gov

Simply trying to load the site if you keep an eye on the loading data in the bottom left you'll see it is constantly trying to maintain a connection but can't. Every page further in the site is like that. This issue didn't appear until after Sunday the 12th build.

Sidenote: Once you log in, if you try clicking on your name in the upper left hand screen it will not show the drop down menu. This is an easier way to understand the issue since get to a "file claim" page is once a week.

Actual results:

While logged into the site to file a claim you're brought to a page with two CSS buttons. Go back or Continue. Selecting the Continue button do nothing. It highlights and depresses but does not bring you to the next page. I have logged in several times over the past few days since Sunday thinking this was the site's issue and not Firefox 80. Today I decided to use Edge to see if it works and there were no issues. Was able to file a claim like normal.

Because I can only file a claim once a week I'm unable to show you the issue until next Sunday by which I'll screenshot it to give you a reference. Knowing what I know of Firefox I believe it has more to do with the loading of the site than the button itself being broken. That's just me though.

"Connecting to https://uplink.in.gov"
"Waiting for https://uplink.in.gov"
"Performing a handshake to https://uplink.in.gov"

Those three prompts rapidily repeating themselves as the page tries to load.

Expected results:

The CSS prompt "Continue" should have progressed me to the next page to continue filing the claim. I believe this issue has something to do with how firefox 80 loads the site information and is failing to.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Emilio Cobos Álvarez (:emilio)]

Thanks for filing this!

Simply trying to load the site if you keep an eye on the loading data in the bottom left you'll see it is constantly trying to maintain a connection but can't. Every page further in the site is like that. This issue didn't appear until after Sunday the 12th build.

I can't reproduce this... If you can repro, can you try to run mozregression and see what broke it?

I'm moderately sure it's not a CSS bug per se given that (though if there are other issues with CSS please let's get them as separate bugs), so trying to find a better component.

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

Trying to load https://uplink.in.gov redirects to https://www.in.gov/dwd/ for me and that load works fine.
I don't see "Continue" anywhere.

Am I possibly missing some step, or does the site look different since I'm loading it from EU perhaps?

Comment 4

[ice2jafar]

After using mogression on all builds between the dates I can't reproduce on any fresh installs. Here's what I've found out so far. I've deleted cache for the site. Issue persists. I've disabled all addons. Issue persists. I've updated Windows to latest build. Issue persists.

This time I'm running side comparisons of both the nightly build and what I have right now. See screenshots below.

This is the page when entering on my build. Notice the three boxes are available immediately.

https://cdn.discordapp.com/attachments/462207225734103051/735500710766051378/3452.png

This is the page when loading a fresh build from mogression. You're immediately introduced with a popup and even after that each box is hidden until you select Yes on the first one.

https://cdn.discordapp.com/attachments/462207225734103051/735501556962820126/unknow3333n.png

Let me know what other actions you'd like me to take. Easiest thing would be for me to just do a reinstall but that'd leave this bug for the next guy. >.> Where'd the fun in that be.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:farre, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

[Neha Kochar [:neha]]

I'm also unable to reproduce, same experience as comment 3.