Responsive design no longer takes effect on reload
Hi,
When using responsive design in FF now, it doesn't reload properly. You can view the page fine. But then if you make a change to the CSS on the website, press reload, and it doesn't always update.
For example, I just edited my CSS, and when I reloaded the page in a responsive mode, it reloaded with the OLD style. However, as soon as I press Ctrl+Shift+M to come back out of responsive, the new CSS has loaded fine and it showing what I *should* have been seeing in responsive.
It never used to do this - so has something broken in a later version?
Thanks
Andy
Solução escolhida
Could be this bug:
- Bug 1497799 - [Firefox Nightly] if I made changes and try to refresh the page in responsive mode, it doesn't update content
(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)
Maybe try one of these forums that are better suited for development related questions.
Ler esta resposta 👍 1Todas as respostas (5)
Any userChrome.css that you use will have to contact the site you got the css if that is the case and if you created your own userChrome.css the help will be hard to do since that was your creation.
Hi,
Sorry I should have been more clear. I'm a developer. Its my own CSS file, and its Firefox that isn't working right. Sometimes when you reload in responsive mode it works fine, but other times it doesn't (and yet when you come out of responsive, it looks exactly as it should). Its like its not rendering the page properly
Cheers
Andy
Solução escolhida
Could be this bug:
- Bug 1497799 - [Firefox Nightly] if I made changes and try to refresh the page in responsive mode, it doesn't update content
(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)
Maybe try one of these forums that are better suited for development related questions.
Thanks - that was it. I guess I'll just have to wait until its fixed then, seeing as there doesn't seem to be a solution :(
I'm still experiencing this issue. In the bug report, looks like they set it to resolved, but it's not. One commenter said as much. Is there anything we can do to help confirm? I saw that we're not supposed to comment there.