Results not displaying

[possumbilities]

Description

From a user via email:

I've used CC before without problems. This time, I chose the license type, filled in the attribution fields, but no 'done' button provided. It just hangs on 'waiting for required fields'.

I filled the option for CC-BY-NC-ND and all of the optional attribution fields. I'm using win10 Pro, Firefox 140.0.4
Can't think of anything else. The 'done'/'back' buttons don't even show up on chooser, so I think it's on your end. No problems with other websites.

It should be noted that the Chooser does not have a Done or Back button anymore as they were redundant in the previous beta version and were removed due to their confusing implementation. The current Chooser live updates once all required fields are entered.

However, despite that confusion of expectation from one version of the Chooser to the other, the results should have displayed given the input they provided above. They claim that all they get is the default "waiting for required fields" message.

Expectation

The results should load if all required fields are entered properly.

Resolution

• I would be interested in resolving this bug.

[possumbilities]

Still unable to reproduce this. Will followup with the original reporter again to see if i can get more details.

[codefromlani]

@possumbilities
I was able to reproduce a browser-specific difference that may help

Firefox:
On Firefox, even after selecting the CC-BY-NC-ND license and filling the attribution fields, the chooser remains stuck on “waiting for required fields.” Additionally, the page appears to load as mostly plain HTML, CSS styling does not seem to be applied.

Chrome:
On Chrome, as soon as the license is selected, the chooser correctly updates to show the “Recommended Choice: CC BY-NC-ND 4.0” results panel.

It seems possible that in Firefox a CSS or asset-loading issue is preventing parts of the interface (and/or JS-driven state updates) from initializing correctly, which could explain why the required-fields state never resolves.

[iamshravanijadhav]

Hi @possumbilities, I’d like to investigate this issue and work toward a fix. The Firefox-specific reproduction from @codefromlani gives a good starting point. I’ll reproduce the issue locally, compare the Firefox and Chrome behavior, and investigate the CSS/asset loading and JavaScript initialization differences.

[possumbilities]

@iamshravanijadhav Please see the Contribution Guidelines. You can begin work, and submit a PR for review at any time.