1124005 - CSS cached in style editor

Status: UNCONFIRMED

(DevTools :: Style Editor, defect, P2)

Description

[Aron Barreira Bordin]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150113033800

Steps to reproduce:

Open a website, go to style editor and change the css. Then, edit the local .css file and reload the page. 


Actual results:

The page loaded use the local css file, however, the style editor keep showing the old one(before a local edit)


Expected results:

The style editor should show the same css being used by the page.

Comment 1

[willmarquardt]

Even if you don't make edits outside of Firefox, it still caches the CSS. Open local page (on local dev server), make a change in style editor, save, refresh. Correct CSS is used for display, but old CSS is shown in style editor.

This is infuriating because then you go make another change and save it just to find that the previous changes have been undone.

Comment 2

[Nancy Poekert]

I can confirm this bug.  The current css file rules were being applied but a previous version of the css file was loaded into the style editor.   When I deleted the cache the current file loaded.

Comment 3

[Patrick Brosset <:pbro>]

Inspector bug triage (filter on CLIMBING SHOES).

Comment 4

[Andrei Ivnitskii]

Firefox 67.0.4
Kubuntu 19.04

I can confirm this bug. Since ~60 version style editor is unusable. I need to close it and open again.

I forced to use Chrome for web development, but I love FF

Comment 5

[Chris]

I have just been working on an intense project and this bug bit me multiple times.

Editing and saving the edited code in FF will often overwrite my current CSS with an older cached version, which was very disconcerting as my clients kept complaining fixes I had already put in place were disappearing.

One of the tells when this is about to happen (I realised only after having to restore my git repo many times) is if you change the CSS in the inspector and then switch to the style editor the recently changed code does not appear.

In this case I simply edited the code and saved it and then found previous changes had gone. As I do not work this way all the time its not a convenient tell.

As far as CSS Editing this has become a showstopper because apart from the above tell (not proven) this appears to be very random and may be related to having multiple browser windows open and several style sheets with the same file name open in the style editor. The only other way is to do a git diff and see if the changes I made are the only changes. if not then start again.

Another possibly related issue with the developer tools is you often get alert messages from different browser windows from completely unrelated domains in your developer tools for the current window. I say this because I often have multiple windows open in one I will have the dev site which I am working on in another tab/window I will have production site with the same stylesheet open but using a different domain. I am wondering if this is somehow connected.

Comment 6

[Chris]

(In reply to Chris from comment #5)

BTW I am on Firefox 68.0.1 (64-bit)

Comment 8

[djjeffkarkiro]

Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:

Describe any areas of concern to which you want the accessibility team to give special attention:

Comment 9

[Phelix Chrome Dev]

try manually clearing the browser cache. sometimes it helps