Workspaces/Persistence 2.0 not persisting Elements changes
Reported by
spanish...@gmail.com,
Feb 15 2017
|
|||||
Issue description
Chrome Version : 56.0.2924.87
OS Version: OS X 10.11.4
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Set up workspaces, following the google guide setup-workflow
2. Edit Styles in the Elements/Styles Tab
3. View unmodified local resources
What is the expected result?
Style changes should persist, or automatically save, to the local files mapped with map to file system resource.
What happens instead of that?
The css style changes are not persisted, and refreshing the page loses all changes.
Please provide any additional information below. Attach a screenshot if
possible.
Editing in the Sources tab does persist changes correctly. I am using a timestamp at the end of my css import scripts for caching reasons.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
,
Feb 16 2017
,
Feb 17 2017
Thank you for the report. On Chrome 56.0.2924.76, this local files should be updated from Elements panel if you see the green checkmark next to the CSS filename. Was it there? Since persistence 2.0 is still experimental, could you please verify that this bug occurs on Chrome Canary? Latest Chrome versions may have fixed these bugs, and this issue might be addressed by the time stable channel is updated.
,
Feb 21 2017
,
Feb 21 2017
There is a green circle indicator next to the CSS classes in the elements tab, I have attached a picture with the green circles. In canary, persistence 2.0 is not working for me. Editing anywhere with a green circle does persist, but editing element.style does not persist.
,
Feb 21 2017
The element.style is, indeed, not persisted. This is intentional: when you edit element.style, you don't edit source - instead you edit the style attribute of the DOM node. That's why there's no green bubble next to the element.style rule. However, we have ideas on making element.style-editing experience more pleasant. I'm closing this for now since this works non-ideal, but as intended. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by erikc...@chromium.org
, Feb 16 2017