Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Style error on landing page first load #199

Closed
bonjourmauko opened this issue Oct 2, 2018 · 2 comments
Closed

Style error on landing page first load #199

bonjourmauko opened this issue Oct 2, 2018 · 2 comments
Assignees
Labels

Comments

@bonjourmauko
Copy link
Member

bonjourmauko commented Oct 2, 2018

.loading CSS rule should not be applied to the list of parameters and variables:

capture d ecran 2018-10-02 a 18 24 16

Reproduce it locally

Set your nginx config to something like this:

http {
  upstream legislation-explorer {
    server localhost:2030;
  }

  server {
    listen      80;
    server_name localhost;

    location ~/legislation(.*)$ {
        proxy_pass http://legislation-explorer$1;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }
  }
}

Then run:

npm install
npm run clean
npm run build
npm start

And visit http://localhost/legislation

@fpagnoux
Copy link
Member

fpagnoux commented Oct 2, 2018

This is really weird:

For the France instance, I cannot reproduce the bug for:

  • Chrome 69
  • Safari 12
  • Firefox 62

Incognito mode doesn't change anything.

However, for the new Demo instance, I experience the bug will all the exact same browsers 😲 .

The two instances are served by the same version of the legislation explorer, with the same version of node, and have the same package-lock.json.

Even weirder, others (@sandcha, @maukoquiroga) experience the bug on the France instance too 😱

@fpagnoux
Copy link
Member

fpagnoux commented Oct 2, 2018

More strangeness:

Going to a variable page, and coming back to the home page, seems to temporarily fix the issue.

This doesn't seem fully deterministic...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants