New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 671882 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit 29 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

[Feature Request] i am a developer and would like the ability to refresh a css file without reloading the page

Reported by artcliff...@gmail.com, Dec 7 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. inspect an element
2. view its style(s)
3. click style sheet reference to view style sheet
4. edit css offline and click refresh button in dev tools to reload style sheet being viewed
Alternative after step 2 above
3. click a refresh button/icon next to a stylesheet link in the styles view

What is the expected behavior?
Reload just the stylesheet and apply changes to the already loaded page

What went wrong?
When deving components that are subcomponents of dialog windows or other workflows that require multiple clicks to get to, it is time consuming and mind-numbing to have to reload the page and go through the workflow to see style changes made to the actual style sheets. While the style tools do allow realtime editing which is nice, it would be easier, when one makes the temporary tweaks in the actual css file(s) it would be a huge time saver to just reload the relevant css file(s).

Did this work before? N/A 

Chrome version: 54.0.2840.99  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

Less menu diving to go from found style to reloading offending stylesheet is preferred.
 
Labels: M-57
Status: Untriaged (was: Unconfirmed)
As the issue is feature request,Marking it as Untriaged to get more inputs from dev team.
Components: Platform>DevTools>Authoring
Owner: lushnikov@chromium.org
Status: Assigned (was: Untriaged)
Ah. ye olde refresh css. :)

Not the worst ideas ever. Lushnikov, we could probably add a button, and somehow tie this into Persistence..
Status: WontFix (was: Assigned)
The new "overrides" feature should cover the use case.

https://umaar.com/dev-tips/162-network-overrides/
Overrides doesn't help this situation. This is more of a Persistence/workspaces thing, as the developer is changing the localhost/css/style.css file and wanting to see the new results.

It's basically a request for this feature: https://www.paulirish.com/2008/how-to-iterate-quickly-when-debugging-css/
In order to make this compelling, we could prompt the user to refresh when we've detected the original CSS file has changed. We'd basically have to poll to do that. 
Yes and no, if editing files directly on a server (for whatever reason)
then I would not be able to point to a local file to check changes on.

Also if I'm collaborating with distributed developers one of whom is saving
changes to CSS and I want to see it without necessarily reloading the whole
page the persistance/workspace thing isn't quite what I was going for.

I was more interested in telling the browser to reload a css file from the
server.

Sign in to add a comment